[9.3] (backport #18537) Remove unused/unreachable rake tasks

[mergify]

Release notes

[rn:skip]

What does this PR do?

Remove any rake task that is not called by a gradle task (or is a dependency of a rake task that is called by a gradle task). This follows up work to remove unused gradle tasks and ensure that all ci entrypoints start in gradle. The only exception are the linting tasks. These may be used in development workflows and may be usedful if we add linting steps to CI in the future.

---

This is an automatic backport of pull request #18537 done by Mergify.

[mergify]

Cherry-pick of 4c15870 has failed:

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

You are currently cherry-picking commit 4c158701.
  (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:   qa/Rakefile
	deleted:    rakelib/docs.rake
	modified:   rakelib/plugin.rake
	deleted:    rakelib/version.rake

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   rakelib/test.rake
	both modified:   rakelib/vendor.rake

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

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
• /run exhaustive tests : Run the exhaustive tests Buildkite pipeline.

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 9a3183c

Failed CI Steps

• :java: Java unit tests - FIPS mode

History

• 💔 Build #4095 failed 9fd648f

cc @donoghuc