🚨🚨 Source Amazon Seller Partner: remove brand analytics reports from cloud

[artem1205]

What

Resolve https://github.com/airbytehq/alpha-beta-issues/issues/1741 and https://github.com/airbytehq/alpha-beta-issues/issues/1493

How

Remove brand analytics reports from cloud, permanently remove deprecated FBA reports

Recommended reading order

1. source.py
2. streams.py

🚨 User Impact 🚨

Removed streams:

• GET_BRAND_ANALYTICS_MARKET_BASKET_REPORT
• GET_BRAND_ANALYTICS_SEARCH_TERMS_REPORT
• GET_BRAND_ANALYTICS_REPEAT_PURCHASE_REPORT
• GET_BRAND_ANALYTICS_ALTERNATE_PURCHASE_REPORT
• GET_BRAND_ANALYTICS_ITEM_COMPARISON_REPORT
• GET_SALES_AND_TRAFFIC_REPORT
• GET_VENDOR_SALES_REPORT
• GET_VENDOR_INVENTORY_REPORT
• GET_FBA_FULFILLMENT_INVENTORY_ADJUSTMENTS_DATA
• GET_FBA_FULFILLMENT_CURRENT_INVENTORY_DATA
• GET_FBA_FULFILLMENT_INVENTORY_RECEIPTS_DATA
• GET_FBA_FULFILLMENT_INVENTORY_SUMMARY_DATA
• GET_FBA_FULFILLMENT_MONTHLY_INVENTORY_DATA

Pre-merge Actions

Updating a connector

Community member or Airbyter

• Grant edit access to maintainers (instructions)
• Unit & integration tests added

Airbyter

If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.

• Create a non-forked branch based on this PR and test the below items on it
• Build is successful
• If new credentials are required for use in CI, add them to GSM. Instructions.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 15, 2023 6:06pm

[github-actions]

Before Merging a Connector Pull Request

Wow! What a great pull request you have here! 🎉

To merge this PR, ensure the following has been done/considered for each connector added or updated:

• PR name follows PR naming conventions
• Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan.
• Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
• You've updated the connector's metadata.yaml file any other relevant changes, including a breakingChanges entry for major version bumps. See metadata.yaml docs
• Secrets in the connector's spec are annotated with airbyte_secret
• All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
• Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example
• Migration guide updated in docs/integrations/<source or destination>/<name>-migrations.md with an entry for the new version, if the version is a breaking change. See migration guide example
• If set, you've ensured the icon is present in the platform-internal repo. (Docs)

If the checklist is complete, but the CI check is failing,

1. Check for hidden checklists in your PR description

2. Toggle the github label checklist-action-run on/off to re-run the checklist CI.

[lazebnyi]

LGTM
Small comment to doc.