fix(referral): wrap LiquidityManagementModule import in forwardRef to break circular dependency

[Danswar]

Summary

• DEV has been crash-looping since PR Add append-only double-entry ledger (monitoring-only) #3880 (AccountingModule) landed: Nest cannot create the ReferralModule instance / The module at index [9] of the ReferralModule "imports" array is undefined, repeating on every restart attempt.
• AccountingModule is now the first import in core.module.ts, and is the first thing to require LiquidityManagementModule. That require transitively re-enters ReferralModule (via LiquidityManagementModule -> BankModule -> UserModule -> ReferralModule) before LiquidityManagementModule's own file finishes exporting. ReferralModule's existing, unwrapped LiquidityManagementModule import then captures undefined at decorator-evaluation time — a classic CommonJS circular-require hazard, not a runtime bug.
• Fix: wrap that one import in forwardRef(), matching the pattern ReferralModule already uses for its other circular deps (UserModule, TransactionModule) in the same file.

Verification

• Reproduced locally: built dist/ off origin/develop unmodified and ran node dist/src/main.js — got the identical ReferralModule crash and scope trace seen in DEV logs.
• Applied the one-line fix, rebuilt, reran — the DI crash is gone; bootstrap proceeds well past module instantiation (next failure is an unrelated missing local JWT secret, expected without env config).
• npx jest --testPathPattern="(referral|liquidity-management|accounting)" — 36 suites / 738 tests passed.
• Full suite via pre-push hook (build + all tests) passed: 237 suites / 4220 tests.

Test plan

• Merge and confirm DEV's dfx-api container stops crash-looping / all Kuma DEV child monitors recover