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/ContactQRScanShowView.vue

@@ -110,6 +110,7 @@ import {
 } from "../libs/endorserServer";
 import { decodeEndorserJwt, ETHR_DID_PREFIX } from "../libs/crypto/vc";
 import { retrieveAccountMetadata } from "../libs/util";
+import { Router } from "vue-router";
 
 @Component({
   components: {
@@ -121,6 +122,7 @@ import { retrieveAccountMetadata } from "../libs/util";
 })
 export default class ContactQRScanShow extends Vue {
   $notify!: (notification: NotificationIface, timeout?: number) => void;
+  $router!: Router;
 
   activeDid = "";
   apiServer = "";