Migrate from Vue2/Vuex => Vue3/Pinia

[planetchili]

Vue2 is in end of life so to avoid unresolvable CVE strikes and to keep up with new features we should migrate to Vue3. Vue3 now works far better with Pinia rather than Vuex, so we should perform that migration as well.

Vue3 has moved from the options API to a new "Composition API" so that will require extensive reworking of the view component logic (particularly since the Class Component style is no longer being well-maintained). Vuetify has support for Vue3 now so it is possible that the template / markup might be largely reused without a complete rewrite. Work will need to be done to determine if all widgets used are still available in Vuetify 3.

[planetchili]

• Upgrade dev environment Node and NPM
• Explore Vite and vuetify scaffolding create functionality for Vue3 / typescript
• Run default test page in AppCef from local dev server
• Import and integrate Vuetify 3 w/ element on test page
• Get the Vue IDE extension working for .vue and typescript in VS Code
• Create VS Code debugger attach config with proper sourcemapping, verify breakpoints and watches
• Import and test Pinia stores with composition api, verify breakpoints in debugger
• Install standalone vue devtools, enable connection from appcef, verify component and Pinia functionality
• Solve issue of 1st load failing with dev server (optimization causing another render proc to spawn?)
• Sourcemapping for JS log entries in pmlog
• Basic vuetify page test with dark theme
• Verify availability of vuetify 2 component via docs
• Survey vuetify migration steps
• Survey vue3 migration steps
• Survey pinia migration steps
• Study Vue3 fundamentals, best practices, and useful techniques
• Study pinia fundamentals, best practices, and useful techniques
• Review Vue-router changes (if any)
• Setup copilot environment and test basic functionality
• Create base App.vue layout with simple view mockup
• Create a test loadout config system to validate dynamic composition and drag and drop compatibility
• Survey API changes and shimming in current UI and determine opportunities for simplification, upgrading, future provision
• Setup a workspace scoped to both the vue2 and new vue3 codebase
• Experiment with copilot migration of views/components using awareness of both codebases
• Experiment with copilot migration of stores
• ETC ETC