Installation method makes no sense

Podman-compose requires podman-compose to get installed.

Here's my timeline:

1. I downloaded latest Podman Desktop binary.
2. I downloaded a binary for podman (that I copied on /usr/bin/). Podman Desktop found it and ran it just fine.
3. Tried to install podman-compose. Any way I tried, it requires podman-compose to be already installed. And I can't install via pip3 either, ubuntu's repos restrict these kinds of installations and make it complicated.

Sure, there is podman-compose on my Linux Mint's repos, but if I install it, it pulls the older podman package too. I want to use the binary that I manually downloaded. I need podman-compose to either have a binary as well (an appimage?) so I can point podman-desktop to it and be done with it.

Review the installation approaches described in the issue, including the binary, pip3, and Linux distribution package paths, and consider how Podman Desktop is expected to locate podman-compose. Done means users can install podman-compose without replacing a manually installed Podman binary, with the supported approach documented clearly.

Written by the indexing model from the issue text.