Connector daily integration tests: new job for alpha connectors

[alafanechere]

What

Declare a separate job to run alpha connectors build only in the daily Connector Integration Tests run.
I reverted #21589 because all the builds can't run in 30mn.
For orchestration and timeout reasons I prefer to declare it in a second job.

[github-actions]

Airbyte Code Coverage

There is no coverage information present for the Files changed

Total Project Coverage	26.77%	🍏

[erohmensing]

I also like having them as 2 separate jobs, in case we end up wanting to point them to different places. Wondering what led us to pick 30 minutes as a timeout for the initial job, and should we have some sort of timeout for this one, even if a longer one?

[erohmensing]

Hm, the alpha connectors are still in here, maybe you need to merge master in to this branch? Just to validate

[alafanechere]

Wondering what led us to pick 30 minutes as a timeout for the initial job.

I don't know exactly but I think it's to have a kind of guarantee that all the test run in 30mn to build the report that is sent on slack afterward in a different action.

And should we have some sort of timeout for this one, even if a longer one?

I hope the default 360mn is good enough.
The scripts of this workflow triggers /test workflow in parallel, I hope that we can build all our alpha connectors in parallel in less than 6hours...
I'll figure out tomorrow 😄