ci(action): auto-bump daily and change slack notification channel

[v1v]

What does this PR do?

Change the slack channel
Run daily

Why is it important?

There will be only 24 hours daily between the golang-crossbuild auto-bumps and this one.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool
• I have added an integration test or an E2E test

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Similar to elastic/golang-crossbuild#367

Use cases

Screenshots

Logs

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

[mergify]

This pull request does not have a backport label. Could you fix it @v1v? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[v1v]

CI error unrelated to this change, it failed when processing the test results

[pierrehilbert]

I fixed the processing step

[v1v]

The CI failures are unrelated to the nature of this PR.

[pierrehilbert]

#3901 will fix the test error

[elastic-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[v1v]

Unrelated CI failures

[v1v]

I have no clue what's the reason for the failure in the CI, but this PR does not change anything that the CI can test/verify. It changes the automation in GitHub actions.

@pierrehilbert, how should we proceed?

[pierrehilbert]

This error is a new one, I'm looking at it to report it and if this can't be related to the change, will force merge this one.

[pierrehilbert]

/test

[elastic-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube