Work Items - Tasks First Time Experience

What does this MR do and why?

Any time a user visits a work item, he should see an alert/info having links to the doc page of gitlab for a detailed explanation. This information will be seen either when a work item(right now task) is viewed in modal/full page view

Screenshots or screen recordings

How to set up and validate locally

Make sure :work_items feature flag is enabled if the changes are not visible in the local environment

Feature.enable(:work_items)

Example below:

1. To create a work item/task , open any issue and create checkboxes/tasks list in the description.
2. When you view the issue after saving and hover over any list item , you will see a small icon at the end of the item , click on that.
3. A modal will be opened , and here is your first work item created when you close it. Now that will be converted to a link.
4. Visit any work item in full page view/modal such as http://127.0.0.1:3000/gitlab-instance-3485f007/Monitoring/-/work_items/505
5. You should see the alert only the first time you visit a task, since you will be testing in your machine the first time , you will see the first time by default but not after that

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.

Related to #366687 (closed)

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

@@ -49,6 +49,9 @@
 .if-merge-request-targeting-stable-branch: &if-merge-request-targeting-stable-branch
   if: '$CI_MERGE_REQUEST_IID && $CI_MERGE_REQUEST_TARGET_BRANCH_NAME =~ /^[\d-]+-stable(-ee)?$/'
 
+.if-merge-request-labels-run-in-ruby3: &if-merge-request-labels-run-in-ruby3
+  if: '$CI_MERGE_REQUEST_LABELS =~ /pipeline:run-in-ruby3/'
+
 .if-merge-request-labels-as-if-foss: &if-merge-request-labels-as-if-foss
   if: '$CI_MERGE_REQUEST_LABELS =~ /pipeline:run-as-if-foss/'
 
@@ -1789,6 +1792,10 @@
     - <<: *if-default-refs
       changes: *code-backstage-patterns
 
+.setup:rules:verify-ruby-2.7:
+  rules:
+    - <<: *if-merge-request-labels-run-in-ruby3
+
 .setup:rules:verify-tests-yml:
   rules:
     - <<: *if-not-ee