Standardize Vue route names

### Description

Route names are inconsistent across the app, which makes them harder for LLMs (and humans) to predict. Standardizing the naming convention would improve navigation reliability.

This is the most intrusive of the three steps since it touches existing functionality and anything that references routes by name. Probably best tackled last, after #7a and #7b are in place.

The kebab case should be preferred over camelCase as it's easier to manipulate in the case of dynamic routes.

### Epic/Story

https://github.com/FlowFuse/engineering/issues/160
https://github.com/FlowFuse/flowfuse/issues/7920

### Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

Review the route definitions and every place that references route names, then read the linked epic and prerequisite issue #7920. Confirm the existing naming patterns and dependencies before changing anything. Done means existing routes and their references consistently use kebab case without breaking navigation.

Written by the indexing model from the issue text.