[FIX] allow users to use the browser-back button

[surchs]

• Closes Add warning not to use browser back button #619
• Closes [ENH] Add component test for tool-navbar #491

Changes proposed in this pull request:

A lot of the stuff in the store around route handling and pages is already taken care of by the router. This PR essentially removes all of this stuff and replaces it with functions from the router

One big issue with the old system was that it only looked to the store to find out what page it was currently on. so if I use the browser back button this is not reflected in the store, but the route changes. So I could end up e.g. on the home page with a state that thinks I'm on the annotation page.

So we can make this both easier and have it not break anymore

• add pageOrder in the store (tricky to do in the router)
• renamed index.vue to home.vue -> so the route name works out
• added test for nav-bar

Checklist

• PR has an interpretable title with a prefix ([ENH], [FIX], [REF], [TST], [CI], [MNT], [INF], [MODEL], [DOC]) (see https://neurobagel.org/contributing/pull_requests for more info)
• PR links to GitHub issue with mention Closes #XXXX
• Tests pass
• Checks pass

For new features:

• Tests have been added

For bug fixes:

• There is at least one test that would fail under the original bug conditions.

[netlify]

✅ Deploy Preview for neurobagel-annotator ready!

Name	Link
🔨 Latest commit	f0f4af2
🔍 Latest deploy log	https://app.netlify.com/sites/neurobagel-annotator/deploys/656a41c42a7b360008b6ae48
😎 Deploy Preview	https://deploy-preview-650--neurobagel-annotator.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 site configuration.

[rmanaem]

Nicely done @surchs! Handling of routes is elegant and easy to understand.
Aside from the comments, I have two 🍒

• I think we can remove getNextPage and setCurrentPage from the store.
• I'd suggest adding a test for using the browser back button to one of the e2e tests.

[surchs]

The e2e test for validate-output-example-synthetic-e2etest.cy.jsjust failed and then passed when rerun. So we're still not quite done with the flaky tests it seems

[rmanaem]

I think you forgot to remove getNextPage and setCurrentPage from the store and add a test for the browser back button.

[surchs]

@rmanaem can you confirm where you still see getNextPage and setCurrentPage in the store? I saw them in the test and removed them there.

[rmanaem]

can you confirm where you still see getNextPage and setCurrentPage in the store?

annotation_tool/store/index.js

Lines 497 to 518 in 86c0abf

	getNextPage(p_state) {
	let nextPage = "";
	switch ( p_state.currentPage ) {
	case "home":
	nextPage = "categorization";
	break;
	case "categorization":
	nextPage = "annotation";
	break;
	case "annotation":
	nextPage = "download";
	break;
	case "download":
	nextPage = "";
	break;
	}
	return nextPage;
	},

annotation_tool/store/index.js

Lines 839 to 842 in 86c0abf

	setCurrentPage(p_state, p_pageName) {
	p_state.currentPage = p_pageName;
	},

[rmanaem]

Thanks @surchs! 🧑‍🍳