fix(vue): navigating between parameterized pages now results in page transition

[liamdebeasi]

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Build (npm run build) was run locally and any changes were pushed
• Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

Issue Number: resolves #22662

What is the new behavior?

• Updated the view matching logic so that /page/1 and /page/2 do not get matched to the same view.
• I previously suggested that we follow what Ionic React does and clone the page element during transition: bug: ionic vue navigating to the same page with a different parameter should still result in a transition #22662 (comment) Upon further investigation, I don't think that is a good idea since swipe to go back would not as it depends on the previous page already being in the DOM. We could choose not to remove the cloned page, but at that point I think it just makes sense to have /page/1 and /page/2 matched to different view items. This logic should probably be implemented in Ionic React as well when bug: react swipe to go back does not implement gesture properly #22342 is fixed.
• Note: Because v5 supports the old child tab setup, this fix cannot be easily backported from v6 to v5. As a result, it will be a v6-only fix.

Does this introduce a breaking change?

• Yes
• No

Other information