Make ContentNode Menus Keyboard accessible

[AlexVelezLl]

Summary

Description of the change(s) you made

Catch keyboard focus when contentNode menus are opened. Added conditional render to menus since Vuetify just mounts the menu once by default, and this does not allow the mounted or destroyed hooks to be executed.

Manual verification steps performed

Verified that these menus are keyboard-accesible now:

1. ContentNode menus.
2. ContentNode deails menus.
3. Breadcrumbs menus.
4. StudioTree elements menus.
5. StudioTree elements context menu.
6. ContentNode context menu.

Screenshots (if applicable)

Compartir.pantalla.-.2024-01-17.08_59_51.mp4

---

Reviewer guidance

How can a reviewer test these changes?

1. Open a channel
2. Navigate to contentNodes Menus with the keyboard

References

Closes #4369

Comments

Keyboard navigation is not entirely consistent for now (the outline color changes for example) But this would be solved when the menu is updated to KDropdownMenu.

---

Contributor's Checklist

PR process:

• If this is an important user-facing change, PR or related issue the CHANGELOG label been added to this PR. Note: items with this label will be added to the CHANGELOG at a later time
• If this includes an internal dependency change, a link to the diff is provided
• The docs label has been added if this introduces a change that needs to be updated in the user docs?
• If any Python requirements have changed, the updated requirements.txt files also included in this PR
• Opportunities for using Google Analytics here are noted
• Migrations are safe for a large db

Studio-specifc:

• All user-facing strings are translated properly
• The notranslate class been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. icons, user-generated text)
• All UI components are LTR and RTL compliant
• Views are organized into pages, components, and layouts directories as described in the docs
• Users' storage used is recalculated properly on any changes to main tree files
• If there new ways this uses user data that needs to be factored into our Privacy Policy, it has been noted.

Testing:

• Code is clean and well-commented
• Contributor has fully tested the PR manually
• If there are any front-end changes, before/after screenshots are included
• Critical user journeys are covered by Gherkin stories
• Any new interactions have been added to the QA Sheet
• Critical and brittle code paths are covered by unit tests

---

Reviewer's Checklist

This section is for reviewers to fill out.

• Automated test coverage is satisfactory
• PR is fully functional
• PR has been tested for accessibility regressions
• External dependency files were updated if necessary (yarn and pip)
• Documentation is updated
• Contributor is in AUTHORS.md

[akolson]

❤️

[akolson]

Just checking this is not string that requires translation?

[AlexVelezLl]

Oh no, these are strings just for analytics purposes.