run packagemanifests: registry server should use world-writable directory to write files

[joelanford]

Description of the change:
Write the bundle.db and termination.log file to /tmp when running the registry server for the run packagemanifests command.

Motivation for the change:
Resolves the issue raised here.

Fixes #3863

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]

@Doout can you try this branch out to see if it resolves this issue you brought up here?

[jmrodri]

/lgtm

[Doout]

@joelanford I comment back on the issues, but still hit the permission denied with this PR.

[openshift-ci-robot]

New changes are detected. LGTM label has been removed.

[joelanford]

@Doout @jmccormick2001 I updated this PR to set the registry pod working directory to /tmp, spun up a 4.5 cluster, and confirmed that the registry pod started successfully with this latest change.

[jmccormick2001]

one thing I noticed is that when the pod, memcached-operator-registry-server-675559c6d5-6fwm5, is started, it is using imagePullPolicy of Always...I wonder if this is intended?

[joelanford]

@jmccormick2001 imagePullPolicy defaults to Always when the image tag is latest; otherwise it defaults to IfNotPresent.

There's probably a separate discussion to be had about whether we should keep using latest, but this is what we've been using for the run packagemanifests command for awhile so that behavior hasn't changed.