🐛 octavia-cli: propagate open api spec update

[alafanechere]

What

Closes #11438

How

• Write integration tests to spot regressions introduced by API changes:
  • Reproduce management of source, destination and connection in octavia-cli/integration_tests/test_apply/test_resources.py . The test configuration files explain the number of new lines in this PR 😄
• Update the model we use to retrieve the source catalog from the API to propagate changes made to the Open API spec in 3d9f9ec . Change from SourceIdRequestBody to SourceDiscoverSchemaRequestBody .
• Run integration tests from the CI (update octavia build job and run a script to run the integration test on a new airbyte instance).

Todo

• Write the same kind of integration test for connection management.
• Run the integration tests in the CI to make builds fail if the test does not pass. The octavia build workflow is triggered if changes are detected in airbyte-api folder (and on the octavia-cli folder of course).

[lmossman]

Had a couple questions about the tests but I don't think they are blocking. The other changes here seem fine to me!

[lmossman]

I don't really understand why these methods are calling remove on state_path? Or why its calling silent_remove() twice?

And similarly, why are the source() and destination() methods calling delete_source()/delete_destination() after yielding them?

[alafanechere]

In the context of pytest fixtures, the code after yielding is considered as the test teardown logic. I'm basically cleaning up state files and remote resources at the end of the test run.