Add Tor support documentation

[ShahanaFarooqui]

• Integrate Tor support into CLN's multi-arch Docker image for amd64, arm64, and arm/v7 platforms.
• Provide documentation detailing the steps to run the CLN container with Tor

[Raimo33]

Who is this assigned to? I'm willing to tackle this.

[ShahanaFarooqui]

@Raimo33 Thanks! I initially spent a day or two on this but had to shift focus due to other priorities.

AFAICT, CLN on Docker is already capable to support Tor with the existing Tor image, with config options like:

always-use-proxy
tor-service-password
proxy
addr
bind-addr
announce-addr

The main gap seems to be a thorough documentation on setting up CLN over Tor with Docker. Let me know if I have overlooked anything and add me as a reviewer once you open the PR.

[Raimo33]

I'm in the process of refactoring the whole docker file. I can't add Tor on this messy dockerfile. I'm willing to start adding Tor support after the refactoring is approved.

Probably in weeks. Feel free to assign this to someone else in the meantime.

[ShahanaFarooqui]

@Raimo33 Just a quick note that there is currently an open PR (#8080) under review that replaces the last remaining Python plugin (wss-proxy). Once merged, this will significantly simplify the Dockerfile refactoring, so it might make sense to wait for that merge before proceeding.

As stated earlier, regarding Tor integration, we might not need to bundle Tor directly in CLN’s Dockerfile. Instead, we could run Tor in a separate container (e.g., using dockurr/tor) and configure the CLN node to route traffic through it.

[Raimo33]

Thank you for the heads up. I was going to remove that wss-proxy workaround anyways.

If you want to run Tor separately, we might need a docker-compose.yml setup. what do you think? Is that overkill?

Personally I think setting up Tor should be on the user side, not something that concerns lightningd