Set a limit of 255 characters for security policy names

What does this MR do and why?

This MR makes the following changes to address the behavior reported in !88679 (comment 1002820788)

• Removes the previous backend truncation of the security policy name at 25 characters
• Introduces a schema limit of 255 characters for security policy names.

Screenshots or screen recordings

Previous behavior

Current behaviour

Existing policies (with name length longer than the new limit)

New policies

How to set up and validate locally

1. Create a group where you are the group owner. This requires a GitLab Ultimate license.
2. Create a project in the group "Development Project"
3. Navigate to the project -> Security & Compliance -> Policies page
4. Create a new Scan Result policy with a long name
5. Click "Configure with a merge request". This will create a new "Security Policy Project" in the same group and will open a merge request in that newly created project.
6. Merge in the auto-generated merge request
7. Navigate back to your "Development Project" and open a merge request in that project
8. View the security approval rule on the MR page

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

.gitlab/ci/rules.gitlab-ci.yml

@@ -1495,6 +1495,12 @@
       changes: ["vendor/gems/mail-smtp_pool/**/*"]
     - <<: *if-merge-request-labels-run-all-rspec
 
+.vendor:rules:ipynbdiff:
+  rules:
+    - <<: *if-merge-request
+      changes: ["vendor/gems/ipynbdiff/**/*"]
+    - <<: *if-merge-request-labels-run-all-rspec
+
 ##################
 # Releases rules #
 ##################