Update export for new planes to make boilerplates work

[NorOldBurden]

What

Fix GraphQL tenant export to include the routing binding plane and the catalog plane, so a redeployed tenant DB can resolve its own subdomains (login was 404-ing).

Why

resolve_route() (routing 6.1.0) reads hostname_bindings/route_bindings/catalog_private.apis. The export produced none of them:

• bindings: no database_id column → the flat {databaseId} filter failed and was silently skipped
• catalog_private.apis: dot-qualified keys are skipped (bare-name collisions in the meta build), and the catalog_sync trigger doesn't fire during replica-mode migration replay

Changes

• pgpm/export: manifest keys + updated_at exclusions for hostname_bindings/route_bindings; TableConfig.filterViaDomainIds; GraphQLClient in-filter support; tenant domain-id pre-fetch
• pgpm/export: derive catalog_private.apis from exported apis rows (mirrors catalog_private.tg_apis_catalog_sync 1:1)
• pgpm/export: remove dead functions manifest key (catalog_private.functions is not exportable via the meta API)

[blacksmith-sh]

Found 2 test failures on Blacksmith runners:

Failures

Test	View Logs
Cross-flow parity: exportMeta vs exportGraphQLMeta/ both flows should produce identical SQL INSERT output for each table	View Logs
Cross-flow parity: exportMeta vs exportGraphQLMeta/ both flows should produce the same set of table keys	View Logs

^{Need help on this PR? Tag @codesmith-bot with what you need.}