fix: convert defineNuxtRouteMiddleware to legacy middleware

[wattanx]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Fixed defineNuxtRouteMiddleware as it needs to be converted to legacy middleware and executed.
Also, abortNavigation has been updated with reference to Nuxt 3.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[danielroe]

Thank you! 👌

[Towerism]

FYI now that this has been released to npm, we cannot use the latest nuxt bridge-edge. Trying to start our application results in a blank page. And an error in the console that states:

composables.mjs:126 Uncaught (in promise) TypeError: Cannot set properties of undefined (setting '_processingMiddleware')
    at _callee$ (composables.mjs:126:40)
    at tryCatch (runtime.js:64:15)
    at Generator.invoke (runtime.js:299:1)
    at Generator.eval [as next] (runtime.js:124:1)
    at asyncGeneratorStep (asyncToGenerator.js:3:1)
    at _next (asyncToGenerator.js:25:1)
    at eval (asyncToGenerator.js:32:1)
    at new Promise (<anonymous>)
    at eval (asyncToGenerator.js:21:1)
    at eval (composables.mjs:136:4)

For now, we have no choice but to use an older version 3.0.0-28109745.a6e6787 which is the last release that doesn't contain this change.

[wattanx]

@Towerism
If possible, could you provide a reproduction?
It will help us to resolve that error quickly.
(It would be helpful if you could also create an issue.)

[Towerism]

@wattanx created issue. includes reproduction. #826