fix(catalog): drop location_name from DataForSEO Maps live

[stonexer]

What this does

Feedback #516: live /serp/google/maps/live/advanced rejects location_name with task status 40501 Invalid Field: 'location_name', the same class as related-keywords filters (#546 / #439) and order_by (#54). catalog_get listed location_name as an alternative to location_code / location_coordinate, so agents sent it.

• Remove location_name from dataforseo.x.serp-google-maps-live-advanced request body params
• Warn in input.note and rewrite the location_code / location_coordinate notes so they no longer treat location_name as an accepted alternative (use location_code or location_coordinate; Live Maps returns 40501)
• Keep cost, path, capability, the location_code: 2840 example, and sibling News live/advanced (still documents location_name)

Fragment updated: docs/context/architecture/catalog.md. Settlement, routing, and credentials are unchanged.

How it was tested

• uv run --frozen python -m pytest -q tests/test_dataforseo_constraints.py tests/test_catalog_api.py::test_catalog_get_dataforseo_maps_live_omits_location_name — 23 passed
• uv run --with pytest-xdist pytest -n auto -q — 4376 passed, 8 skipped
• CI on this branch is green (test, test-postgres, gitleaks)

Checklist

• uv run --with pytest-xdist pytest -n auto -q passes locally
• Added or updated tests for the change (if it affects behavior)
• Updated the relevant docs/context/ fragment (if a subsystem changed)
• No secrets in the diff (keys, tokens, .env values)