Combine TransactionsGraphql and Transactions streams into a single Transactions stream in the catalog

[girarda]

What

• Combine Transactions and TransactionsGraphql under a single Stream from the user's perspective
• This should smooth out the migration a bit by letting the users only care about what matters. they don't need to decide whether to use the bulk or rest api - only whether they care about the user_id field

How

• Modify select_transactions_stream to return the right implementation for the transactions stream instead of filtering them from the list of streams
• Add a CAT with the new config field. A new test config was added to google secret manager

Recommended reading order

1. airbyte-integrations/connectors/source-shopify/source_shopify/source.py
2. airbyte-integrations/connectors/source-shopify/source_shopify/streams/streams.py
3. airbyte-integrations/connectors/source-shopify/unit_tests/test_source.py
4. airbyte-integrations/connectors/source-shopify/integration_tests/configured_catalog.json
5. airbyte-integrations/connectors/source-shopify/acceptance-test-config.yml

[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	Jan 29, 2024 7:04pm

[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.

[alafanechere]

Approving on behalf of connector ops the change to the acceptance-test-config.yml file.

[girarda]

closing because this was already added to #32345