fix: bind community docker wallet to default key path

[zigengZ]

Summary

This PR updates the community Docker setup so the operator wallet is mounted at both key paths used by the container runtime:

• /app/wallet.json
• /app/hb/hyperbeam-key.json

It also keeps priv_key_location explicitly set to /app/wallet.json and documents that both paths must point to the same wallet.

Why

The Docker entrypoint writes priv_key_location to /app/wallet.json, while HyperBEAM can also use its default key path under /app/hb/hyperbeam-key.json.

Mounting the same wallet at both paths keeps the configured key path and runtime default key path aligned, so the node exposes the intended signer consistently.

How to use

Create the operator wallet at the repository root:

wallets/operator.json

For example, if the repository is checked out at ~/HyperBEAM, the full path is:

~/HyperBEAM/wallets/operator.json

Then start the community Docker stack from docs/community:

cd docs/community
docker compose up --build -d

The compose file references the wallet from that directory as:

../../wallets/operator.json

and mounts the same file into the container at both runtime key paths:

/app/wallet.json
/app/hb/hyperbeam-key.json

No extra environment variable is required for this wallet binding.

Validation

• git diff --check origin/feat/community-node..HEAD
• bash -n docs/community/entrypoint.sh