[8.1](backport #2159) jjbb: daily job with branch aliases

[mergify]

This is an automatic backport of pull request #2159 done by Mergify.
Cherry-pick of bccd485 has failed:

On branch mergify/bp/8.1/pr-2159
Your branch is up to date with 'origin/8.1'.

You are currently cherry-picking commit bccd485.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   .backportrc.json
	modified:   .ci/e2eTestingFleetDaily.groovy
	modified:   .ci/e2eTestingHelmDaily.groovy
	modified:   .ci/e2eTestingK8SAutodiscoveryDaily.groovy
	new file:   .ci/jobs/e2e-testing-schedule-daily.yml
	new file:   .ci/schedule-daily.groovy
	modified:   .mergify.yml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .ci/jobs/e2e-testing-fleet-daily-mbp.yml
	both modified:   .ci/jobs/e2e-testing-helm-daily-mbp.yml
	both modified:   .ci/jobs/e2e-testing-k8s-autodiscovery-daily-mbp.yml

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[elasticmachine]

💔 Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-02-22T17:05:15.141+0000

• Duration: 67 min 36 sec

Test stats 🧪

Test	Results
Failed	1
Passed	248
Skipped	0
Total	249

Test errors

Expand to view the tests failures

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / [empty] – TEST-x86_64-kubernetes-autodiscover-f7db10e0-2022-02-22-17:38:53.xml

• no error details
Expand to view the stacktrace

 Test report file /var/lib/jenkins/workspace/PR-2167-2-7de3dda9-93d1-4899-93e2-f63a0de81b9a/outputs/3.131.142.255/TEST-x86_64-kubernetes-autodiscover-f7db10e0-2022-02-22-17:38:53.xml was length 0 

Pipeline error

This error is likely related to the pipeline itself. Please go to the traditional console output here" You will see the error (either a wrong syntax or configuration)

🐛 Flaky test report

❕ There are test failures but not known flaky tests.

Expand to view the summary

Genuine test errors

💔 There are test failures but not known flaky tests, most likely a genuine test failure.

• Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / [empty] – TEST-x86_64-kubernetes-autodiscover-f7db10e0-2022-02-22-17:38:53.xml

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.