Internal routes present in application-level files

[zainforbjs]

Describe the bug
Browser test fixture routes are currently defined inside config/settings.cfm, which is intended for application-level (developer-defined) configuration. These routes appear to be part of Wheels core functionality and not something end users should manage or modify.

Current routes in config/routes.cfm:

// Browser test fixture routes (loginAs endpoint is env-gated in controller)
.scope(path="/_browser")
    .get(name="browserTestHome", pattern="/home", to="BrowserTestHome##index")
    .get(name="browserTestLogin", pattern="/login", to="BrowserTestSessions##new")
    .post(name="browserTestAuthenticate", pattern="/login", to="BrowserTestSessions##create")
    .get(name="browserTestDashboard", pattern="/dashboard", to="BrowserTestHome##dashboard")
    .post(name="browserTestLogout", pattern="/logout", to="BrowserTestSessions##destroy")
    .get(name="browserTestLoginAs", pattern="/login-as", to="BrowserTestLogin##create")
.end()

To Reproduce
Steps to reproduce the behavior:

1. Create a new Wheels application
2. Open config/routes.cfm
3. Observe the presence of browser test fixture routes defined alongside user configuration

Expected behavior
Core/internal routes (such as browser testing fixtures) should be defined within the framework itself (e.g., vendor/wheels/public/routes.cfm) rather than in config/routes.cfm.

Application config files should remain focused on developer-defined settings and routes only.

Screenshots

Desktop:

• OS: Any