Remove OCI Env

[fao89]

Initial PR for removing OCI Env,
I'll start other PRs for improving the docs and makefile
Issue: AAP-32608

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[patchback]

Backport to stable-4.9: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply baaa371 on top of patchback/backports/stable-4.9/baaa3710d5b7bf705ea7a0c6a28741680d72e379/pr-2445

Backporting merged PR #2445 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible/galaxy_ng.git
3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-4.9/baaa3710d5b7bf705ea7a0c6a28741680d72e379/pr-2445 upstream/stable-4.9
4. Now, cherry-pick PR Remove OCI Env #2445 contents into that branch:

   $ git cherry-pick -x baaa3710d5b7bf705ea7a0c6a28741680d72e379
   If it'll yell at you with something like fatal: Commit baaa3710d5b7bf705ea7a0c6a28741680d72e379 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x baaa3710d5b7bf705ea7a0c6a28741680d72e379
5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Remove OCI Env #2445 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-4.9/baaa3710d5b7bf705ea7a0c6a28741680d72e379/pr-2445
7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to stable-4.10: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply baaa371 on top of patchback/backports/stable-4.10/baaa3710d5b7bf705ea7a0c6a28741680d72e379/pr-2445

Backporting merged PR #2445 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible/galaxy_ng.git
3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-4.10/baaa3710d5b7bf705ea7a0c6a28741680d72e379/pr-2445 upstream/stable-4.10
4. Now, cherry-pick PR Remove OCI Env #2445 contents into that branch:

   $ git cherry-pick -x baaa3710d5b7bf705ea7a0c6a28741680d72e379
   If it'll yell at you with something like fatal: Commit baaa3710d5b7bf705ea7a0c6a28741680d72e379 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x baaa3710d5b7bf705ea7a0c6a28741680d72e379
5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Remove OCI Env #2445 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-4.10/baaa3710d5b7bf705ea7a0c6a28741680d72e379/pr-2445
7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.