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

@@ -134,7 +134,7 @@
 <script lang="ts">
 import * as R from "ramda";
 import { Component, Vue } from "vue-facing-decorator";
-import { RouteLocation, Router } from "vue-router";
+import { RouteLocationNormalizedLoaded, Router } from "vue-router";
 
 import QuickNav from "../components/QuickNav.vue";
 import TopMessage from "../components/TopMessage.vue";
@@ -150,6 +150,8 @@ import { Contact, ContactMethod } from "../db/tables/contacts";
 })
 export default class ContactEditView extends Vue {
   $notify!: (notification: NotificationIface, timeout?: number) => void;
+  $route!: RouteLocationNormalizedLoaded;
+  $router!: Router;
 
   contact: Contact = {
     did: "",
@@ -164,7 +166,7 @@ export default class ContactEditView extends Vue {
   AppString = AppString;
 
   async created() {
-    const contactDid = (this.$route as RouteLocation).params.did;
+    const contactDid = this.$route.params.did;
     const contact = await db.contacts.get(contactDid || "");
     if (contact) {
       this.contact = contact;