Upgrade to Vue 3

[RayBB]

Closes #7547

Overview

This PR upgrades Vue. Due to Vue's architecture, this requires upgrading all Vue-related dependencies simultaneously.

Changes Needed

• Fixed styling issues in Library Explorer
• Restored Merge UI functionality by adding async plugin globally (temporary solution approved by @cdrini)
• Fixed the kebab_case function to work with acronyms
• Update eslint config https://eslint.vuejs.org/user-guide/#configuration-eslintrc
  • This caused precommit to auto fix destroyed -> unmounted and beforeDestroy -> beforeUnmount
  • Make another ticket to upgrade the linter to use plugin:vue/vue3-recommended (which will make many automatic changes for best practices) use vue recommended sytles #10339
• Updated the HelloWorld to be Vue 3

Technical Details

• Considered externalizing Vue dependencies but kept current bundling approach since:
  1. We rarely (never?) have multiple Vue components per page
  2. It would work with a CDN but we don't want that
  3. Current build process is simpler to maintain
• Minification is enabled via Vite's default settings

Implementation Notes

• Approach checked with Vue.js and Vite communities (they didn't have a better way):
  • Vue Discord Discussion
  • Vite Discord Discussion
• While alternative bundlers (Parcel/Webpack) could work, Vite provides official documentation for our use case

Testing Instructions

docker compose up
docker compose run --rm home make components
# visit http://localhost:8080/explore?ol_base=openlibrary.org

To test the dev setup run (outside of docker)

npm install --no-audit
COMPONENT="LibraryExplorer" npm run serve

TBH, I'm not really sure if this is needed but we already had it so I updated it.

Test the following components:

• ✅ Library Explorer (use http://localhost:8080/explore?ol_base=openlibrary.org for prod data)
• ✅ Merge UI
• ✅ Observation Form (feedback about books a user gives)
• ✅ Edition Identifiers
• ✅ Barcode Scanner
• ✅ BulkSearch

Stakeholders

@cdrini

confidence and access to the correct context to evaluate and use this code. -->

[cdrini]

I think we might want to roll this back to the options API version ; we're still recommending the options API for Open Library for consistency with existing components and for being easier to use on simple cases -- which is most of Open Library's components.

[cdrini]

Wooohooo!!!! Great work @RayBB !!! This has stumped the team for multiple attempts 😁 This works perfect across all our components, and all the tech decision you've made here make perfect sense! Thank you!!

[cdrini]

😂