Upgrade pulp-web image to latest nginx image

[gerrod3]

& fix publishing both arm+amd variants

fixes: #644
fixes: #702

[bmbouter]

This all looks good to me!

[patchback]

Backport to 3.63: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.63/02ebce228d9ef7332d39f3a5be6418cc2106d193/pr-703

Backported as #704

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

[patchback]

Backport to 3.28: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 02ebce2 on top of patchback/backports/3.28/02ebce228d9ef7332d39f3a5be6418cc2106d193/pr-703

Backporting merged PR #703 into latest

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/pulp/pulp-oci-images.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/3.28/02ebce228d9ef7332d39f3a5be6418cc2106d193/pr-703 upstream/3.28

4. Now, cherry-pick PR Upgrade pulp-web image to latest nginx image  #703 contents into that branch:

   $ git cherry-pick -x 02ebce228d9ef7332d39f3a5be6418cc2106d193

   If it'll yell at you with something like fatal: Commit 02ebce228d9ef7332d39f3a5be6418cc2106d193 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 02ebce228d9ef7332d39f3a5be6418cc2106d193

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Upgrade pulp-web image to latest nginx image  #703 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.28/02ebce228d9ef7332d39f3a5be6418cc2106d193/pr-703

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 3.22: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 02ebce2 on top of patchback/backports/3.22/02ebce228d9ef7332d39f3a5be6418cc2106d193/pr-703

Backporting merged PR #703 into latest

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/pulp/pulp-oci-images.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/3.22/02ebce228d9ef7332d39f3a5be6418cc2106d193/pr-703 upstream/3.22

4. Now, cherry-pick PR Upgrade pulp-web image to latest nginx image  #703 contents into that branch:

   $ git cherry-pick -x 02ebce228d9ef7332d39f3a5be6418cc2106d193

   If it'll yell at you with something like fatal: Commit 02ebce228d9ef7332d39f3a5be6418cc2106d193 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 02ebce228d9ef7332d39f3a5be6418cc2106d193

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Upgrade pulp-web image to latest nginx image  #703 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.22/02ebce228d9ef7332d39f3a5be6418cc2106d193/pr-703

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 3.39: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.39/02ebce228d9ef7332d39f3a5be6418cc2106d193/pr-703

Backported as #706

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

[patchback]

Backport to 3.49: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.49/02ebce228d9ef7332d39f3a5be6418cc2106d193/pr-703

Backported as #705

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