feat(vue): add `key` and `meta`, and re-export `createBeforeEachHandlers`

[zanmato]

This adds key and meta to the route context, and re-exports the beforeEach routing handlers from $app/index to allow the developer to override these methods. Also adds an i18n example (vue-i18n) that has both locale prefix and domain routing, by overriding the above methods and properties.

Checklist

• [x] run npm run test and npm run benchmark
• [x] tests and/or benchmarks are included
• [x] documentation is changed or added
• [x] commit message and code follows the Developer's Certification of Origin and the Code of conduct

[netlify[bot]]

✅ Deploy Preview for agitated-mahavira-26f8f9 ready!

Name	Link
🔨 Latest commit	eb7fd40962a44676133268dcb62b3af8c0a3d5d9
🔍 Latest deploy log	https://app.netlify.com/projects/agitated-mahavira-26f8f9/deploys/689b02ca6a0ff400081fdfde
😎 Deploy Preview	https://deploy-preview-244--agitated-mahavira-26f8f9.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[zanmato]

@galvez I think this is a better approach, see the first commit for the changes to the vue package, and the second commit on how I've overridden the routing creation to enable i18n routing. The routing file is a bit verbose, but I don't think we could shorten it that much to be honest

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: eb7fd40962a44676133268dcb62b3af8c0a3d5d9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR