[9.1] (backport #8746) ci: revert deployment_csp_configuration.yaml to create_deployment_csp_configuration.yaml

[mergify]

What does this PR do?

This PR renames deployment_csp_configuration.yaml back to create_deployment_csp_configuration.yaml (introduced by this PR) as this file is currently used by the github action, which runs from main, and bump the ESS version for our CI integration tests. Thus the name of this file needs to stay same across all release branches that the former PR doesn't have to be in.

Why is it important?

Because we need to have working github actions

Checklist

• I have read and understood the pull request guidelines of this project.
• 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

Disruptive User Impact

None, this change is solely regarding the CI

How to test this PR locally

This change affects only the CI so no local testing is possible, open a draft PR against main 🙂

Related issues

• Reverts part of Integration Test: upgrade Integrations Server in ECH #8417

  ---

  This is an automatic backport of pull request ci: revert deployment_csp_configuration.yaml to create_deployment_csp_configuration.yaml #8746 done by Mergify.

[mergify]

Cherry-pick of 2252fdd has failed:

On branch mergify/bp/9.1/pr-8746 Your branch is up to date with 'origin/9.1'. You are currently cherry-picking commit 2252fdd7c. (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) Unmerged paths: (use "git add <file>..." to mark resolution)	both modified: .mergify.yml	both modified: test_infra/ess/readme.md no changes added to commit (use "git add" and/or "git commit -a") 

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

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[pkoutsovasilis]

cherry-picking this one on top of #8745