Move work item dev widget to main body and create MR and branch

What does this MR do and why?

Move work item dev widget to main body and add create entity

To give more context - since some decisions were made mid-milestone regarding placement of the dev widget , Create MR/branch from a work item (!172232 - closed) was scrapped midway.

Related issues

1. Move work item development widget to main body (#507749 - closed)
2. 🚀 Development Widget: Create MR from Developmen... (#477785 - closed)
3. 🚀 Development Widget: Create branch from dev wi... (#477531 - closed)

This MR covers the following :

header	header
Create Merge request split dropdown with the "add design" button in the main body
Movement of dev widget inside the main body
Add dropdown in the dev widget to create branch and MR
Options dropdown in MR item and branch item

App

References

Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.

MR acceptance checklist

• Do not show dev widget when empty
• Do not show create branch/MR when work_items_alpha is off since it also touches "production tasks"
• The new CTA's are behind work_items_alpha
• Show tooltip on truncate MR long name
• Truncate long name of branches
• Make sure the create CTA split button in main body is available only on work items with dev widget (for example not available on epics but only issues and tasks)
• The tooltip in dev widget is available when we have closing merge requests which will autoclose the work item
• The main body create MR is not available when the ability to create branches does not exist
• [ ]

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

1. In rails console enable the FF

   Feature.enable(:work_items_alpha)

2. Create any issue/task with new issue look on , and see that you are not able to see the dev widget in the main body
3. Create a branch with the split button in the main body and see you that can the dev widget with the branch in the main body(real time update not available right now)
4. Create any MR for the issue/task and write "Resolves #id" in the description, come back to the issue and see the MR
5. You can also try linking the issue with any feature flag and see that pop up in the main body

See that there is no regression when the work_items_alpha is off and production tasks

Related to #427975 (closed) Resolves #477785 (closed) Resolves #477531 (closed) Resolves #507749 (closed)

.gitlab/ci/test-on-omnibus/main.gitlab-ci.yml

@@ -322,8 +322,7 @@ ldap-no-server:
     - if: $QA_SUITES =~ /Test::Integration::LDAPNoServer/
     - !reference [.rules:test:manual, rules]
 
-# TODO: re-enable after gitlab-org/quality/quality-engineering/team-tasks#3153 is resolved
-.ldap-tls:
+ldap-tls:
   extends: .qa
   variables:
     QA_SCENARIO: Test::Integration::LDAPTLS
@@ -332,8 +331,7 @@ ldap-no-server:
     - if: $QA_SUITES =~ /Test::Integration::LDAPTLS/
     - !reference [.rules:test:manual, rules]
 
-# TODO: re-enable after gitlab-org/quality/quality-engineering/team-tasks#3153 is resolved
-.ldap-no-tls:
+ldap-no-tls:
   extends: .qa
   variables:
     QA_SCENARIO: Test::Integration::LDAPNoTLS