Rename IT folders

[gbanasiak]

This is to differentiate between it.conftest from Rally and it.conftest from Rally tracks.

[esbenchmachine]

💔 All backports failed

Status	Branch	Result
❌	9.2	Backport failed because of merge conflicts You might need to backport the following PRs to 9.2: - CI determines Elasticsearch build arguments using unified job in gh workflow [stateful] (#925) - Exclude some challenges when testing with ES release builds (#922) - Reduce filtering scope in CI workflow (#908) - Address pytest deprecations (#911) - Fix pytest skip argument (#905) - Solves problems with expensive inlinestats benchmarks (#896) - Adds better challenges for comparing inlinestats (#873) - Change backport labeling pattern to vX.Y

Manual backport

To create the backport manually run:

backport --pr 938

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

[esbenchmachine]

💔 All backports failed

Status	Branch	Result
❌	9.2	Backport failed because of merge conflicts You might need to backport the following PRs to 9.2: - CI determines Elasticsearch build arguments using unified job in gh workflow [stateful] (#925) - Exclude some challenges when testing with ES release builds (#922) - Reduce filtering scope in CI workflow (#908) - Address pytest deprecations (#911) - Fix pytest skip argument (#905) - Solves problems with expensive inlinestats benchmarks (#896) - Adds better challenges for comparing inlinestats (#873) - Change backport labeling pattern to vX.Y

Manual backport

To create the backport manually run:

backport --pr 938

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

[esbenchmachine]

💚 All backports created successfully

Status	Branch	Result
✅	9.2

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

[esbenchmachine]

@gbanasiak
A backport is pending for this PR. Please add all required vX.Y version labels.

• If it is intended for the current Elasticsearch release version, apply the corresponding version label.
• If it also supports past released versions, add those labels too.
• If it only targets a future version, wait until that version label exists and then add it.
  (Each rally-tracks version label is created during the feature freeze of a new Elasticsearch branch).

Backporting entails:

1. Ensure the correct version labels exist in this PR.
2. Ensure backport PRs have backport label and are passing tests.
3. Merge backport PRs (you can approve yourself and enable auto-merge).
4. Remove backport pending label from this PR once all backport PRs are merged.

Thank you!