opal-ci: Use the Fedora container registry

The Fedora images in the Docker hub container registry are updated less
frequently and lag the ones from Fedora's offical repo.

In my experience, this often leads to periods where our CI testing is
broken on rawhide due to some short-lived issue that is already fixed in
current images.

So, change our Dockerfiles to pull specifically from the upstream
registry.fedoraproject.org instead.
Signed-off-by: Reza Arbab <arbab@linux.ibm.com>
Reviewed-by: Dan Horák <dan@danny.cz>
Reviewed-by: Abhishek Singh Tomar <abhishek@linux.ibm.com>

opal-ci/Dockerfile-fedora-rawhide

-FROM fedora:rawhide
+FROM registry.fedoraproject.org/fedora:rawhide
 RUN dnf -y update
 RUN dnf -y install --allowerasing wget curl xterm gcc git xz make diffutils findutils expect valgrind valgrind-devel ccache dtc openssl openssl-devel gcc-powerpc64-linux-gnu mbedtls-devel which qemu-system-ppc
 # for building documentation and the coverage report

opal-ci/Dockerfile-fedora37

-FROM fedora:37
+FROM registry.fedoraproject.org/fedora:37
 RUN dnf -y update
 RUN dnf -y install --allowerasing wget curl xterm gcc git xz make diffutils findutils expect valgrind valgrind-devel ccache dtc openssl openssl-devel gcc-powerpc64-linux-gnu mbedtls-devel which qemu-system-ppc
 # for building documentation and the coverage report

opal-ci/Dockerfile-fedora38

-FROM fedora:38
+FROM registry.fedoraproject.org/fedora:38
 RUN dnf -y update
 RUN dnf -y install --allowerasing wget curl xterm gcc git xz make diffutils findutils expect valgrind valgrind-devel ccache dtc openssl openssl-devel gcc-powerpc64-linux-gnu mbedtls-devel which qemu-system-ppc
 # for building documentation and the coverage report