update default opm index image for run bundle(-upgrade)

[joelanford]

Signed-off-by: Joe Lanford [email protected]

Description of the change:
Update default base image used in run bundle and run bundle-upgrade to the multi-arch quay.io/operator-framework/opm:latest image.

Motivation for the change:
To support non-amd64 clusters and to avoid using the latest master build of opm (which is what quay.io/operator-framework/upstream-opm-builder:latest points to). The quay.io/operator-framework/opm:latest image is the latest tagged release of opm

See also: operator-framework/operator-registry#762

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

[joelanford]

/hold

The shell in the new image is at a different location. I think we may need to symlink /busybox/sh to /bin/sh in the new image.

[joelanford]

/hold cancel

Removed the hardcoded executable paths in the entrypoint script we run. Now it relies on whatever PATH is configured in the image, which works for both quay.io/operator-framework/upstream-opm-builder and quay.io/operator-framework/opm

[camilamacedo86]

That seems ok for me.
It was using the latest tag before.
However, it maybe would be nice in the future we start to work with OPM tags as well.
Otherwise, it might begin to fail because of some change that was not tested.

/lgtm

[rashmigottipati]

Just one suggestion.

/lgtm

[rashmigottipati]

/lgtm

[jmrodri]

/lgtm