Make Flask subdomain matching configurable via SUBDOMAIN_MATCHING

[mreid-tt]

Background:

In PR #142 we bumped Flask (2.3.3→3.1.0) and Werkzeug (3.0.1→3.1.3), which inadvertently disabled Flask’s default subdomain routing behavior. As a result, our blueprints registered with subdomain="api" and subdomain="packages" no longer matched incoming requests on those hosts, breaking key endpoints in production.

What this PR does:

• Adds a new SUBDOMAIN_MATCHING flag to config.py, defaulting to False for local development.
• In the Flask factory (app.py), reads SUBDOMAIN_MATCHING and sets app.subdomain_matching accordingly.

Why this is required:

• Restores blueprint routes on api.<domain> and packages.<domain> that stopped matching after the Flask/Werkzeug upgrade.
• Keeps local development flows intact (using localhost) without subdomains.

Usage:

• Dev: leave SUBDOMAIN_MATCHING=False in config.py.
• Prod: set SUBDOMAIN_MATCHING=True (via your production config) to re-enable subdomain‐based routing.

Fixes: #144

[mreid-tt]

Hey @publicarray, do you think you might have some time over the weekend to issue a new release and deploy these (and any other pending) fixes to the production server?

[publicarray]

Yea i'll give it a go tonight

[publicarray]

The new version is live 🚢