feat(docker): add data persistence to docker-compose

[unwrap-nicolas]

Description and Notes

fixed #795

this PR addresses the lack of data persistence and network flexibility in the current docker-compose.yml setup.

currently, users running docker compose up experience:

• Data loss on container restart — blockchain data, Prometheus metrics, and Grafana dashboards are lost every time containers are recreated
• Mainnet-only — no way to run on signet, testnet, or other networks without manually editing the compose file

Changes

Data Persistence:

• Adds named Docker volumes for Floresta, Prometheus, and Grafana
• Supports FLORESTA_DATA environment variable to reuse existing local blockchain data (useful for sharing data between native and Docker installations)

Network Configuration:

• Adds NETWORK environment variable to easily switch between Bitcoin networks (bitcoin, signet, testnet, testnet4, regtest)
• Forces fixed internal ports (50001 for Electrum, 8332 for RPC) with --rpc-address and --electrum-address flags, avoiding port conflicts when changing networks

Documentation:

• Updates doc/docker.md with examples for running different networks and using local data directories

How to verify the changes you have done?

Start the stack: docker compose up -d or NETWORK=signet FLORESTA_DATA=$HOME/.floresta docker compose up

[luisschwab]

Should be marked as draft until 639 is merged

[Davidson-Souza]

Why does this need #639? I think you can just drop it and leave the persistence part

[unwrap-nicolas]

@Davidson-Souza actually, my goal with this PR is to get the monitoring stack running 100% smoothly with docker-compose.

One issue I noticed was the lack of persistence. However, while fixing that, I realized that PR #639 doesn't fully accomplish its goal of "provisioning grafana dashboards via docker-compose"

But your point makes sense. I've updated this PR's description and removed those specific fixes. I also added them as suggestions on PR #639.

Thanks for the review!