feat: 13818 create StudioContentMenu

[standeren]

Description

Create StudioContentMenu as a reusable component across SettingsModal, ResourceAdm and soon in ContentLibrary.

Settingsmodal

Old menu in settingsmodal:

New menu in settingsmodal:

ResourceAdm

Old menu in ResourceAdm:

New menu in ResourceAdm:

Related Issue(s)

• #{issue number}

Verification

• Your code builds clean without any errors or warnings
• Manual testing done (required)
• Relevant automated test added (if you find this hard, leave it and we'll help out)

[codecov]

Codecov Report

Attention: Patch coverage is 94.79167% with 5 lines in your changes missing coverage. Please review.

Project coverage is 95.28%. Comparing base (4333644) to head (42ad227).
Report is 31 commits behind head on main.

Files with missing lines	Patch %	Lines
...ntentMenu/StudioMenuTab/StudioMenuTabContainer.tsx	80.00%	3 Missing ⚠️
...rc/components/StudioContentMenu/utils/dom-utils.ts	91.30%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #13847      +/-   ##
==========================================
- Coverage   95.29%   95.28%   -0.01%     
==========================================
  Files        1653     1653              
  Lines       22024    22022       -2     
  Branches     2589     2586       -3     
==========================================
- Hits        20988    20984       -4     
- Misses        790      793       +3     
+ Partials      246      245       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[wrt95]

Great job implementing this new @studio/component @standeren! 👏
I can see that we are at least doing four different things in this PR:

• Creating the new component (core)
• Making use of the new component in settings-modal (domain2)
• Making use of the new component in resourceadm.
• Deleting the old component.

As our focus these days are smaller PRs and splitting the them, I suggest splitting this PR into 4 PRs based on the list I wrote above 😄 It will then be easier to review the code, and test the different areas separately. And other reason is so the relevant sub-teams (core, domain2, and resourceadm) will be able to review and test the code in «their area» without affecting each other 😄
What do you think about this?

[standeren]

Great job implementing this new @studio/component @standeren! 👏 I can see that we are at least doing four different things in this PR:

• Creating the new component (core)
• Making use of the new component in settings-modal (domain2)
• Making use of the new component in resourceadm.
• Deleting the old component.

As our focus these days are smaller PRs and splitting the them, I suggest splitting this PR into 4 PRs based on the list I wrote above 😄 It will then be easier to review the code, and test the different areas separately. And other reason is so the relevant sub-teams (core, domain2, and resourceadm) will be able to review and test the code in «their area» without affecting each other 😄 What do you think about this?

Can try to do so!

[standeren]

Here is the first: #13898
Need to wait for this one to be merged before I can create the others

[wrt95]

Here is the first: #13898 Need to wait for this one to be merged before I can create the others

Great @standeren 😄 I'll take a look at it asap 🚀
You can still create the others as draft I believe?

[standeren]

You can still create the others as draft I believe?

Yes, but wont those need to include the changes in the first one anyway? Of course I can merge with main when the contentMenu is merged. I'll see what I find best to do!

[standeren]

Closing this one in favor of multiple, smaller PR's;

• Create the StudioContentMenu studio component
• Use the StudioContentMenu in SettingsModal
• Use the StudioContentMenu in ContentLibrary