feat: Avoid close Tags drawer on edit

[ChrisChV]

Description

• To avoid lose user data
• Wrap with ContentTagsDrawerSheet to build drawer on MFE

Supporting information

• Github issue: [Tagging] Change behaviour of Tag Drawer on click outside openedx/modular-learning#209
• This PR doesn't include:

The footer of the drawer animates to draw the user's attention to the actions (see Figma). Perhaps like Blink 2 at this link

• Internal ticket: FAL-3711
• Depends on: [FC-0036] Refined tag drawer openedx/frontend-app-authoring#939

Testing instructions

• Use this branch of edx-platform: Bump openedx-learning to support tagging with multiple taxonomies at once [FC-0036] openedx/edx-platform#34490
• Run make requirements on cms shell.
• Make sure you have some sample taxonomy/tags data setup: https://github.com/open-craft/taxonomy-sample-data
• Go into a course and click on "Manage tags" option for any unit/block to open the tags drawer
• Click on Edit tags
• Delete a tags and verify that can't close drawer when clicking outside.
• Cancel and verify that you can close drawer when clicking outside.
• Click on Edit tags
• Add new tags and verify that can't close drawer when clicking outside.

[yusuf-musleh]

@ChrisChV Great work on this, the code looks good to me and it works well!

However I am still able to close the drawer when pressing escape even when there are unsaved changes. It might be worth adding some logic to the keypress handler to prevent it from closing when there are unsaved changes.

[ChrisChV]

@yusuf-musleh Thanks for the review!

However I am still able to close the drawer when pressing escape even when there are unsaved changes. It might be worth adding some logic to the keypress handler to prevent it from closing when there are unsaved changes.

Thanks for catch that! I fixed that here: f4d7e04

[yusuf-musleh]

👍 @ChrisChV Great work! Thanks for addressing the issue, its working as expected. For the codecov issue that is failing in the CI, sometimes it gets fixed when re-triggering the CI to run again, I usually do that by doing git commit --amend --noedit and then force pushing, it makes no changes to the code, just changes the commit hash because we are amending (nothing) to it.

• I tested this: Followed testing instructions
• I read through the code
• I checked for accessibility issues
• Includes documentation

[ChrisChV]

Close in favor of openedx#965