SAT: add test case to check supported_sync_modes field is not empty

[alafanechere]

What

Closing #13027
Pydantic is already validating that the list of supported_sync_modes contains only full_refresh or/and incremental but this field is not declared as required (it's a TODO).
Before attempting a protocol change, SAT can ensure this rule is enforced.
I don't think this will solve https://github.com/airbytehq/airbyte-internal-issues/issues/587 as the source-e2e-test is a java connector. @pedroslopez do you confirm I can't run SAT on a java source?

How

Add a test to check that all streams defined in a catalog have the supported_sync_modes field set to a nonempty list.

NB: I added some Pytest syntactic sugar to lighten the conditional raise in the unit test with the does_not_raise context.

🚨 User Impact 🚨

All connector builds that are not passing this new test will fail.

[alafanechere]

/test connector=bases/source-acceptance-test

🕑 bases/source-acceptance-test https://github.com/airbytehq/airbyte/actions/runs/2692228513
✅ bases/source-acceptance-test https://github.com/airbytehq/airbyte/actions/runs/2692228513
No Python unittests run

Build Passed

Test summary info:

All Passed

[pedroslopez]

Nice job!

@pedroslopez do you confirm I can't run SAT on a java source?

SATs can be run against any source, regardless of the language it's implemented in or whether it uses our CDK or not. We should be able to run SAT on source-e2e-test, but it looks like we haven't yet moved the java connectors to use the new SAT (see issue #5176)

[alafanechere]

/publish connector=bases/source-acceptance-test auto-bump-version=false

🕑 Publishing the following connectors:
bases/source-acceptance-test
https://github.com/airbytehq/airbyte/actions/runs/2696226423

Connector	Did it publish?	Were definitions generated?
bases/source-acceptance-test	✅	❌

if you have connectors that successfully published but failed definition generation, follow step 4 here ▶️