There aren't any more pipes in the Dockerfile so it's not needed and
it's ignored by Podman.

- Use the asc format instead of the gpg DB. APT starts ignoring these
  files with the warnings that this is an unsupported filetype.
- Move them to /etc/apt/keyrings while I was at it. It's the new proper
  place for them.

Not sure why this change fixes the build, but it does.

Just want `ansi2txt` to easily strip color codes.

1. Skip the health check requests in the logs.
2. Allow health checks from nonroutable IP addresses.

The OS packages come with a version of packaging. Installing a different
version with Pip is not possible as it requires uninstalling the OS
version which doesn't have all of the needed metadata, therefore the Pip
constraint. Instead of updating the contraint manually everytime it's
updated in Debian, use the version that's currently installed and it
should always be OK (hopefully).

Some packages are now available in the community repo for 3.20 so
there's no need for the edge community repo (and it breaks the build).

Migrated from https://git.shore.co.il/nimrod/resolver.

The Docker CLI and podman-remote.

This reverts commit 86e0e33a.

# Conflicts:
#	workbench/Dockerfile

An older version than the one in Debian is being required and the Debian
version is being uninstalled. Removing the Debian package will remove
gyp and npm. The Python uninstallation fails so let's try to force the
version in Debian instead.

Until https://github.com/aws/aws-cli/issues/8342 is resolved, AWS CLI v2
can't be used with Python 3.12. But v1 is.

I think that the build failure is fixed in a newer version of the
package. Let's see if something fails to install with this constraint.

They've updated the supported versions.