Support Deploying Containers with `podman-compose` (rootless)

[ben-krieger]

Describe the bug 🪲
Attempting to use podman-compose as a drop-in replacement for docker-compose does not work.

To Reproduce 🪜
Steps to reproduce the behavior:

1. Same, except podman compose up -d

Expected behavior
Same result as with docker-compose

Screenshots 🖼️
N/A

AMT Device (please complete the following information): 🖥️
N/A

Service Deployment (please complete the following information): ⛈️

• Deployment Type: Docker (using Podman)
• Node Version: N/A
• Component & Version: v2.26.0

Additional context

To get podman (rootless) to work for OpenAMT to work, I had to take the following measures:

1. Set "dns_enabled": true in /etc/containers/networks/podman.json
2. Modify kong's ports in docker-compose.yml to expose 8443:8443 rather than 443:8443
3. Modify webui's environment in docker-compose.yml to include port 8443 in {MPS,RPS,VAULT}_SERVER env vars
4. Either ignore the healthcheck status on mpsrouter or patch podman-compose to get the correct status (Fix CMD healthchecks running with /bin/sh containers/podman-compose#1106)

[ben-krieger]

Proposed solution:

• Update docs to note requirement for using podman with DNS enabled in network config
• Update docker-compose.yml to make kong port configurable
• Update docs to include port where currently only host IP is mentioned (implicit 443)
• (Optional) Update docs to include note on unhealthy mpsrouter container when using podman-compose