fix: routing compatibles encoding and resolve

[BobbieGoede]

Description

This PR changes logic and reverts #76 and makes my other PR #78 obsolete if this is merged.

Based on https://router.vuejs.org/guide/migration/#-route-properties-Encoding it looks like we shouldn't do additional encoding, and personally I think it would be better to leave it up to the router resolve when and where to encode.

I tried to remove any where possible and fixed type issues based on the function usage.

Linked Issues

• May resolve LocalePath double encoding URLs, causing 404s nuxt-modules/i18n#2523
• Resolves Hash in NuxtLink don't work with LocalePath nuxt-modules/i18n#2525

Additional context

It's possible I have made bad assumptions about the types 😬 please let me know if this is the case.

Hopefully I can remove some of the exclusions/splits between the Vue 2 and Vue 3 routing in a future PR.

[kazupon]

Hopefully I can remove some of the exclusions/splits between the Vue 2 and Vue 3 routing in a future PR.

Yeah 😅

When I started the project for this package, I made nuxt i18n v8 to work with both Nuxt Bridge and Nuxt 3.

nuxt i18n v8 is currently only available for Nuxt 3.
And the composable for nuxt i18n v7.4 that @wattanx is working on targets the nuxt i18n v8 composables (useLocalePath and etc) to port.
I think that @intlify/routing should be integrated into nuxt v8 for maintenance reasons.

This integration should be a TODO for nuxt i18n v9 after the official release of nuxt i18n v8.

[kazupon]

LGTM!