chore(source-facebook-marketing): sync fork to upstream 5.2.12 (Meta API v25) + attribution_spec

[gvillafanetapia]

What

Upgrades our forked source-facebook-marketing to talk to Meta Marketing API v25, ahead of Meta's June 9, 2026 sunset of all API versions < v24.0. Closes ClickUp 86ba59424.

• Syncs the connector from upstream airbytehq/airbyte: 4.1.0 (API v23) → 5.2.12 (API v25), facebook-business 23.0.0 → ^25.0.0.
• Re-applies our only fork patch: the attribution_spec field on the ad_sets stream.
• Connector version set to 5.3.0.

Upstream contribution of the attribution_spec patch is tracked in airbytehq#78541 (replaces the previously-closed airbytehq#59655).

⚠️ Breaking change (from upstream 5.0.0)

• Removed 7d_view / 28d_view attribution-window columns and wish_bid.
• Custom-insights streams now use level-based primary keys.
• Action required after deploy: refresh schema and reset affected streams.

Follow-up (operational, not in this PR)

• Build & push the fork connector image tagged 5.3.0.
• Update the Airbyte deployment connector version, run a sync, validate campaigns / adsets / ads / ads_insights dev → stage → prod before June 9, 2026.

Can this PR be safely reverted and rolled back?

• YES 💚
• NO ❌ (schema reset required; revert needs care)

[github-actions]

👋 Welcome to Airbyte!

Thank you for your contribution from MuttData/airbyte! We're excited to have you in the Airbyte community.

Helpful Resources

• PR Guidelines: Check our guidelines for contributions.
• Developing Connectors Locally: Learn how to set up your environment and develop connectors locally.
• If you enable BYO Connector Credentials within your fork, you can view your test results here:
  

PR Slash Commands

As needed or by request, Airbyte Maintainers can execute the following slash commands on your PR:

• /format-fix - Fixes most formatting issues.
• /bump-version - Bumps connector versions.
• /run-connector-tests - Runs connector tests.
• /run-cat-tests - Runs CAT tests.
• /build-connector-images - Builds and publishes a pre-release docker image for the modified connector(s).

If you have any questions, feel free to ask in the PR comments or join our Slack community.

Tips for Working with CI

1. Pre-Release Checks. Please pay attention to these, as they contain standard checks on the metadata.yaml file, docs requirements, etc. If you need help resolving a pre-release check, please ask a maintainer.
   • Note: If you are creating a new connector, please be sure to replace the default logo.svg file with a suitable icon.
2. Connector CI Tests. Some failures here may be expected if your tests require credentials. Please review these results to ensure (1) unit tests are passing, if applicable, and (2) integration tests pass to the degree possible and expected.
3. (Optional.) BYO Connector Credentials for tests in your fork. You can optionally set up your fork with BYO credentials for your connector. This can significantly speed up your review, ensuring your changes are fully tested before the maintainers begin their review.

📝 Edit this welcome message.