Verify non-analytics routes remain registered when analytics disabled

[Copilot]

The test for analytics being disabled only verified that analytics GET routes were skipped, but didn't confirm that essential POST routes (/sign-up, /sign-in, /sign-out) remained functional.

Changes

Enhanced skips analytics routes when analytics are disabled test to verify:

• Analytics GET routes are not registered (existing)
• All three POST authentication routes are registered with correct paths, options, and handlers (new)

// Now verifies both what's disabled and what remains active
expect(app.get).not.toHaveBeenCalled();
expect(app.post).toHaveBeenCalledTimes(3);

const signUpRoute = app.post.mock.calls.find(([path]) => path === '/sign-up');
expect(signUpRoute).toBeDefined();
expect(signUpRoute?.[1]).toEqual(expect.any(Object));
expect(signUpRoute?.[2]).toEqual(expect.any(Function));
// Similar checks for /sign-in and /sign-out

Additional Notes

Addresses review feedback from #1802 requesting verification that core authentication functionality remains intact when analytics is disabled.

Testing Checklist

• I tested the feature thoroughly, including edge cases
• I verified all affected areas still work as expected
• Automated tests were added/updated if necessary
• Changes are backwards compatible with any existing data, otherwise a migration script is provided

Visual Changes (if applicable)

N/A - test-only changes

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud