fix(analytics): stale test paths after refactor to lib/services

[PierreBrisorgueil]

Problem

After the refactor(analytics): move from module to lib (#3325) commit, the analytics test files in modules/analytics/tests/ still mock the old module path ../../analytics/services/analytics.service.js instead of ../../../lib/services/analytics.js.

Failing tests:

• analytics.service.resilience.unit.tests.js — init() is async but called without await, client never set, so error propagation tests fail (methods no-op due to if (!client) return)
• analytics.identify.unit.tests.js — mocks ../../analytics/services/analytics.service.js but auth.controller.js now imports from ../../../lib/services/analytics.js, so the mock is never hit

Affected file(s)

• modules/analytics/tests/analytics.service.resilience.unit.tests.js
• modules/analytics/tests/analytics.identify.unit.tests.js

Steps to reproduce

1. Clone Node stack at devkit-node/master (c01d0a9)
2. npm run test:coverage
3. Both analytics test files fail (10 test failures total)

[PierreBrisorgueil]

This was already resolved by the refactor commit 3dbee88 (PR #3325). The test files were moved from modules/analytics/tests/ to lib/services/tests/ and all import paths were updated in the same commit. All 99 analytics tests pass (8 suites), and the full unit suite (400 tests, 30 suites) is green.