[Portal vNext — demo] Portal ↔ CKAN linkage + bespoke-catalogue retire
Replace the bespoke Django/Angular catalogue with links into CKAN. **Delivered** across facility-service `1.4.0`, test-access-service `2.0.0`, backend, and frontend: `facility_ref` + `catalogue_datasets_url` (facility & equipment) and `publish_dataset_url` on the backend; bespoke catalogue views/services/models/routes deleted; facility→catalogue and test-report→publish links live; nav Browse/Register already existed. Design & rationale in this issue's history + `data-access-service/docs/eosc-roadmap.md §3.3`.
## Remaining
- **Prefill** the CKAN new-dataset form from the publish deep-link → marinerg-i/ckanext-marinerg#5 (needs a running CKAN stack to verify).
- **Equipment-detail catalogue link** — backend field is ready; the frontend equipment-detail view is a stub, so the link has no UI home yet. Wire it when that view is built.
## Deploy (infra)
Set `DJANGO_CATALOGUE_URL` + `DJANGO_PORTAL_URL` in the env vaults and rebuild the backend image, or the linkage fields return `null` (safe — no broken URLs).
See also marinerg-i/data-access-service#11 (dissolve the emptied repo).
issue