Enable Multi-Arch Building and Pushing for registry viewer

[Jdubrick]

What does this PR do / why we need it

Updates CI to allow for the registry viewer to be built for multiple architectures. A list of changes are explained below:

• Added scripts/build_multi_arch.sh which allows for the registry viewer to be built and pushed for multiple architectures. This script also supports both podman and docker so we are free to use whatever engine is available. Currently we are using docker as part of the github actions where this script is being called.
• Added github action setups for both qemu and docker buildx to ci.yaml and pushimage-next.yaml to support the building of multi-arch images.
• Added a new timeout value to our main Dockerfile so that Yarn install will not timeout prematurely. When building for a different architecture the emulation can be slow and Yarn was timing out before completion.
• Previously the landing-page and registry-viewer apps were calling a docker-build command as part of our CI to check the builds. These commands have been split so there are dedicated commands for each architecture. Previously by combining them and building with buildx for multi-arch was running into context issues.

Which issue(s) does this PR fix

fixes devfile/api#1548

PR acceptance criteria

• Unit Tests
• E2E Tests
• Documentation
  Update the sidebar if there is a new file added or an existing filename is changed

How to test changes / Special notes to the reviewer

[maysunfaisal]

Does this mean a build might take close to one hour when this action runs?

[Jdubrick]

The longest I've observed so far is around 30 minutes, I just increased it so we have a buffer since it is known to take a while. If GitHub supports arm64 runners in the future (the ones we use and not the large runners in which they now support arm), we'd be able to build the arm64 image in minutes.

[maysunfaisal]

/lgtm

just one simple Q.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Jdubrick, maysunfaisal

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 [Jdubrick]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment