[ITAS] Integration tests for all empty streams in source-stripe

[maxi297]

In order to gain confidence in the change for concurrent CDK incremental, we want to add a layer of tests before performing the change. Those tests should validate the HTTP requests that are performed, the number of records returned by the source and the state value for full refresh and incremental syncs. Those tests should be implemented for all the empty streams i.e.:

• application_fees (IncrementalStripeStream)
• application_fees_refunds (UpdatedCursorIncrementalStripeLazySubStream)
• authorizations (IncrementalStripeStream)
• bank_accounts (UpdatedCursorIncrementalStripeLazySubStream)
• cards (IncrementalStripeStream)
• early_fraud_warnings (UpdatedCursorIncrementalStripeStream)
• external_account_bank_accounts (UpdatedCursorIncrementalStripeStream)
• external_account_cards (UpdatedCursorIncrementalStripeStream)
• payment_methods (UpdatedCursorIncrementalStripeStream)
• persons (Persons) extracted to [ITAS] source-stripe - persons #33348
• reviews (IncrementalStripeStream)
• transactions (IncrementalStripeStream)
• events (Events)

Given that this does not inflate the scope of the issue too much, it would be interesting to explore the different ways to generate mocked responses i.e.

• From an actual response (we might have some data on the events streams
• From the API documentation
• From the OpenAPI spec
  If we could have a very high level estimation of that is the easiest way and what work would be needed to make it work, that would be fantastic!

Blocked by:

• [ITAS] As a tester, I want to safely mock HTTP requests so that I don't have to rely on the actual API #32868
• [ITAS] As a tester, I want to easily be able to create API responses from the API doc so that I don't have to craft fake response myself #32869
• [ITAS] Provide tooling to run source.read from the entrypoint #32870

Acceptance Criteria

• All empty streams are covered
• Many devs have implemented tests

[maxi297]

User impacting things discovered while doing integration tests:

• Paging for authentication issues: https://github.com/airbytehq/airbyte-internal-issues/issues/2812

• Too many requests on availability checks (first case I checked in prod does 2395 requests on availability check): https://github.com/airbytehq/airbyte-internal-issues/issues/2346

• Incremental syncs less frequent than monthly lose data: https://github.com/airbytehq/airbyte-internal-issues/issues/2368

• Deprecated API: Source Stripe: sources API deprecated #33714

• Availability check always validate both full_refresh and incremental with state even though they use different endpoints: https://airbytehq-team.slack.com/archives/C02U9R3AF37/p1703088174082619

• Cursor value is not right: https://airbytehq-team.slack.com/archives/C02U9R3AF37/p1703102031753579

• We don't use API filtering for early_fraud_warnings stream: https://airbytehq-team.slack.com/archives/C02U9R3AF37/p1702669077956759