Update python and ansible, remove preview image

[oceanc80]

Description of the change:

• Updates Ansible to 2.15.0
• Limits dependencies we manage by only including in the Pipfile:
  • ansible-core
  • ansible-runner
  • ansible-runner-http
  • kubernetes
  • urllib3 (need to pin this to a version <2 due to some issues encountered when running the testdata/ansible/memcached-operator with these changes)
• Updates Python to 3.9 (minimum supported by Ansible 2.15.0)
• Removes the ansible-2.11-preview image
• Updates the base.Dockerfile to use multi-stage builds where Rust is installed before installing necessary python packages so that any architecture that may be missing prebuilt wheels can have the wheels built during the image build process.

Motivation for the change:

• Prevent users from using out of date and no longer supported ansible, python packages, and ansible collections

Checklist

If the pull request includes user-facing changes, extra documentation is required:

• [ ] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
• [ ] Add or update relevant sections of the docs website in website/content/en/docs

[leifmadsen]

I think a lot (if not all) of the changes to things outside the release/ansible folder will end being synced downstream with the next upstream SDK release (v1.31.0). To prevent sync issues due to divergence I think we should hold this PR until v1.31.0 is downstreamed and then rebase this PR against the master branch.

/hold

Yea I just noticed that this is changing 410 files. That seems like a lot :)_

[everettraven]

/hold cancel

[everettraven]

/retest

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 74e49e81bfef171456e39a075ca24bd4dae2bc8e and 2 for PR HEAD 0ced4a9c1e31c7a78e7a67223a7a7d2ebb1a0674 in total

[leifmadsen]

I'm a bit confused about the 391 changed files. Is this typical, or is a rebase required here?

[everettraven]

I'm a bit confused about the 391 changed files. Is this typical, or is a rebase required here?

@leifmadsen I think this is typical since we updated some dependencies that are required to be vendored in. I don't think the vendoring will be necessary once the cachito stuff is in but if I understand correctly in the meantime we need to still vendor the new versions in.

[oceanc80]

/retest-required

[oceanc80]

/retest-required

[joelanford]

/test unit

[openshift-ci[bot]]

@oceanc80: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[grokspawn]

/lgtm

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: everettraven, grokspawn, oceanc80

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/openshift/ocp-release-operator-sdk/blob/master/OWNERS)~~ [everettraven,grokspawn,oceanc80] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment