Add new kebab menu items and refactor structure for quick edit modals

[AlexVelezLl]

Summary

Description of the change(s) you made

• Add more options and dividers to menu content node.
• Refactor modals code structure

Note: I was stuck on making the menu keyboard-accessible due to some issues with the way Vuetify handles menus. So I opened a follow up issue for this.

Screenshots (if applicable)

Menu on large screens

Menu on smaller screens

References

Addresses #3414

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]

Generally the code in this file looks good. However, the code is beginning to look repetitive(particularly the options--<VListTile>s) and this may not be good for maintenance. A possible way to deal with the repetition would be to introduce an options data array and use a for loop to create the options.(This is not a blocker, but its worth considering)

[akolson]

Hi @AlexVelezLl ! Code generally looks good. Just a few thoughts on how we could improve the way we generate the options, but this is not a blocker 🙂

[AlexVelezLl]

Thanks! @akolson I have just updated the PR with the refactored code including a new "groupedOptions" computed property to dynamically render the options of the menu!

I will merge this PR since this is a blocker for other PRs but we can update this approach later if needed!