Change the schedule and add a concurrency group to the NightlyBuildsCheck.yml

[hmeriann]

Sometimes the NightlyBuildsCheck.yml workflow starts before the InvokeCI completes running.

This PR moves the schedule to be triggered at 11 CEST daily.

We would like to have older runs got cancelled when there is a new run of the NightlyBuildsCheck.yml had been triggered.

This PR adds concurrency group to manage that.

The future work is to make InvokeCI call the NightlyBuildsCheck.yml to avoid running it by the schedule, which can start before the InvokeCI completed.

[carlopi]

I will finish review later, for now I looked at coordination.

[hmeriann]

As discussed with @carlopi , schedule should stay till the workflow run will be triggered by InvokeCI

[carlopi]

I think possibly something is off, the pushed code do not looks to be behaving as described.
In particular, cron is now missing.

[carlopi]

Also noticing there are many jobs like CI / Build (jekyll gem) (3.9, ubuntu-latest, 3.3) (pull_request), I would guess those can be removed.

[carlopi]

Possibly https://github.com/duckdb/duckdb-build-status/blob/main/.github/workflows/ci.yml can be just removed

[hmeriann]

I think possibly something is off, the pushed code do not looks to be behaving as described. In particular, cron is now missing.

Sorry, put it back

[carlopi]

This as it's now will not work, I think the cron step needs do be in a separate workflow that then needs to create both a job for main and a job for v1.2-histrionicus.

[hmeriann]

There were some more problems which I've just fixed and created a new triggering workflow in another repo to test.