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

@@ -111,6 +111,7 @@ export default class ImportAccountView extends Vue {
   AppString = AppString;
 
   $notify!: (notification: NotificationIface, timeout?: number) => void;
+  $router!: Router;
 
   apiServer = "";
   address = "";
@@ -130,7 +131,7 @@ export default class ImportAccountView extends Vue {
   }
 
   public onCancelClick() {
-    (this.$router as Router).back();
+    this.$router.back();
   }
 
   public isNotProdServer() {
@@ -170,7 +171,7 @@ export default class ImportAccountView extends Vue {
       await db.settings.update(MASTER_SETTINGS_KEY, {
         activeDid: newId.did,
       });
-      (this.$router as Router).push({ name: "account" });
+      this.$router.push({ name: "account" });
       // eslint-disable-next-line @typescript-eslint/no-explicit-any
     } catch (err: any) {
       console.error("Error saving mnemonic & updating settings:", err);