support port-forwarding ranges with docker-compose

[mikedep333]

It turns out that although podman-compose does not support it, docker-compose can forward dynamic port ranges to a port on multiple containers of the same service.

So ports 24716 through 24816 (on the host) can be forwarded to 101 pulp_content containers, all listening on port 24816.

Similarly, 24817 through 24917 (on the host) can be forwarded to 101 pulp_content containers, all listening on port 24817.

podman-compose will ignore this syntax without erroring.

[mikedep333]

This is low-priority because there are no known actual users who have a need for the reverse proxy outside of the docker compose.

The draft PR was sufficient for @bmbouter 's performance testing.