refactor: improve router type safety and usage

- Add explicit Router type imports across views
- Replace $router type casting with proper typing
- Use $router.back() instead of $router.go(-1) for consistency
- Add proper route and router typings to components
- Clean up router navigation methods
- Fix router push/back method calls

This commit improves type safety and consistency in router usage across
the application's view components.

src/views/InviteOneAcceptView.vue

@@ -55,6 +55,7 @@ import { generateSaveAndActivateIdentity } from "../libs/util";
 @Component({ components: { QuickNav } })
 export default class InviteOneAcceptView extends Vue {
   $notify!: (notification: NotificationIface, timeout?: number) => void;
+  $router!: Router;
 
   activeDid: string = "";
   apiServer: string = "";
@@ -123,7 +124,7 @@ export default class InviteOneAcceptView extends Vue {
 
         // That's good enough for an initial check.
         // Send them to the contacts page to finish, with inviteJwt in the query string.
-        (this.$router as Router).push({
+        this.$router.push({
           name: "contacts",
           query: { inviteJwt: jwt },
         });