Harden release readiness and packaging

[TacoRocket]

What changed

• fixed ARM ID normalization for internal joins used by network-ports, workloads, and related endpoint correlation
• fixed the Azure extras packaging constraint so fresh .[azure] installs resolve azure-mgmt-sql correctly
• improved all-checks help and README guidance so operators know it is a longer-running grouped validation path
• added the missing feature-complete, API-mapping, roadmap, and release-process docs needed for a coherent release boundary
• modernized packaging metadata and verified wheel/sdist builds plus fresh install smoke tests

Why

The sister-repo live validation showed the remaining red state was in AzureFox behavior and release readiness rather than missing lab coverage. This PR hardens the current Phase 1-3 boundary so we can stabilize and ship with a truthful install story, consistent operator UX, and reproducible package artifacts.

Operator impact

• network-ports no longer misses joins when Azure ARM IDs differ only by resource-group casing or trailing slash shape
• fresh editable installs with pip install -e '.[azure]' now work on this machine without manual SQL package intervention
• azurefox help now includes all-checks in the root command list and better runtime expectations
• release docs now match the validated build/install workflow instead of a looser source-only path

Validation

• python3 -m ruff check src tests scripts
• PYTHONPATH=src python3 scripts/generate_schemas.py
• PYTHONPATH=src python3 -m pytest tests/test_collectors.py tests/test_golden_outputs.py tests/test_contract_schemas.py tests/test_cli_smoke.py tests/test_help.py tests/test_terminal_ux.py tests/test_models.py
• PYTHONPATH=src python3 -m pytest
• /tmp/azurefox-release-venv/bin/python -m build
• fresh venv wheel install + azurefox help + fixture-backed whoami smoke
• fresh venv editable install with pip install -e '.[azure]' and azurefox help smoke
• pre-push guardrail: python3 -m ruff check . and python3 -m pytest -m "not integration"