fix(vue): canGoBack now returns correct result with initial load redirect

[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?

Previously, we set an initial location history view item no matter the path. This was to work around some undefined errors when on the initial page (if there was no previous page). This was wrong as it set a location history item even for an initial page redirect. This results in canGoBack being wrong as there were always 2+ items in the history stack.

What is the new behavior?

• No longer set initial route, let that happen naturally by listening to the data vue router gives us.

Does this introduce a breaking change?

• Yes
• No

Other information