applications/crossbar: register cb_lists in default modules

[noahmehl]

Problem

GET /v2/accounts/{id}/lists returns 404 on a default deployment.

The Match List module (cb_lists_v1 / cb_lists_v2) ships with crossbar and backs the lists endpoint. Live callflow modules cf_dynamic_cid and cf_lookupcidname depend on this data for caller-ID matching. But 'cb_lists' was never listed in ?DEFAULT_MODULES (applications/crossbar/src/crossbar.hrl), so nothing loads the module and the route is silently dead.

git log -S shows cb_lists has never been in ?DEFAULT_MODULES across the entire history of the file — including the pre-fork 2600Hz history. This is a longstanding upstream bug, not a fork regression. (Same class of silently-dead-route bug as the recent acdc module-registration fix, but a simpler fix since cb_lists is native to crossbar.)

Fix

Add the base atom 'cb_lists' to ?DEFAULT_MODULES.

?DEFAULT_MODULES holds base names. At startup start_mod('cb_lists') fails to find a plain cb_lists module and falls back to maybe_start_mod_versions/2 (crossbar_init.erl), so the single entry loads both cb_lists_v1 and cb_lists_v2 — no per-version entry needed.

Notes / scope

• Existing deployments: a deployment that already persisted an autoload_modules value to its DB won't pick up the new default until that config is flushed/reset. Documented in the commit; no migration code added (kept surgical).
• Data migration out of scope: cb_lists_v2:maybe_migrate/1 is a separate, per-account maintenance concern invoked from crossbar_maintenance:migrate/1; it is neither triggered nor required by loading the module.
• Added a Match list glossary entry to CONTEXT.md disambiguating it from contact lists (cb_contact_list) and blacklists (cb_blacklists).

Testing

• Verified alphabetical placement between cb_limits and cb_media.
• Verified via crossbar_init that base-name loading covers both _v1 and _v2.

[ruhnet]

good!