Remove sudo requirement (PROJQUAY-4630)

[HammerMeetNail]

• Removes requirements for root
• Updates default quay-install location to be in a user writeable directory, $HOME/quay-install
  • Users can use the --quayRoot, --quayStorage and pgStorage flags to change install location, but previous root requirement is needed.
    *Example: $ ./mirror-registry install -v --quayRoot /home/doconnor/quay-install --quayStorage /home/doconnor/quay-install/quay-storage --pgStorage /home/doconnor/quay-install/pg-data
• Stores postgres data in new podman named volume quay-postgres-data
• Removes actions that require /etc/hosts to be updated
  • Only root users can update /etc/hosts, this is incompatible with a rootless install
• Also works on RHEL9 (PROJQUAY-3084)
• Updates mirror-registry to v1.3.0 and includes Quay 3.8.0 for IPv6 support

[doconnor@doconnor-omr-dev-rhel9 ~]$ cat /etc/redhat-release
Red Hat Enterprise Linux release 9.1 (Plow)
[doconnor@doconnor-omr-dev-rhel9 ~]$ podman --version
podman version 4.2.0
[doconnor@doconnor-omr-dev-rhel9 ~]$ systemctl --user status quay-app
● quay-app.service - Quay Container
     Loaded: loaded (/home/doconnor/.config/systemd/user/quay-app.service; enabled; vendor preset: disabled)
     Active: active (running) since Mon 2022-12-19 13:55:52 UTC; 4min 59s ago
    Process: 67021 ExecStartPre=/bin/rm -f /run/user/1007/quay-app.service-pid /run/user/1007/quay-app.service-cid (code=exited, status=0/SUCCESS)

[HammerMeetNail]

CI will fail because we don't allow changes to CI from open PRs. Probably going to require a follow up PR or two to sort out CI.

[jonathankingfc]

Can we still keep the named volume somewhere inside quay_root? I think we should keep the ability that a user can specify their pg mount path especially since it can get quite large over time.

[HammerMeetNail]

I was running into permissions errors as a non-root user when using bind mounts with the postgres container. The postgres user is different than the non-root user and I was having trouble writing to quay_root. Tried a couple different things, but couldn't get it working. Not sure if it's an selinux thing, but dropping in a named volume worked so I went with it. Maybe you know how I can work around user permissions?

[jonathankingfc]

SELinux forces you to set special permissions on a directory before being able to mount it. That is the reason for these steps in each of the service setup tasks. https://github.com/quay/mirror-registry/blob/main/ansible-runner/context/app/project/roles/mirror_appliance/tasks/install-postgres-service.yaml#L7 Maybe we have to update the user there?

[jonathankingfc]

LGTM