feat: improve relay announce and bootstrap handling

[NiKrause]

Summary

This PR improves relay address publication and browser bootstrap handling:

• add support for explicit announced relay multiaddrs via LIBP2P_ANNOUNCE_ADDRS
• separate plain websocket and secure websocket listener ports in go-peer
• let js-peer prefer explicitly configured browser-dialable relay bootstrap addresses when present
• keep delegated-routing discovery as a fallback
• refresh the Go libp2p / AutoTLS-related dependency stack used by the relay

Why

Some deployments expose externally reachable relay addresses that should be announced explicitly rather than inferred locally.

In practice, a relay may have multiple useful public transport paths, but browser clients still need a clear and reliable bootstrap address set. This PR improves how the UC relay publishes those addresses and how js-peer consumes browser-dialable bootstrap addresses.

This also helps deployment environments such as Aleph Cloud, where externally reachable addresses are assigned outside the guest and need to be injected into relay announcements, but the main goal of this PR is runtime/bootstrap correctness rather than deployment workflow changes.

The dependency refresh is included because the newer go-libp2p / p2p-forge stack is required by the current AutoTLS integration and authentication flow.

Scope

This PR intentionally stays focused on runtime/connectivity behavior:

• go-peer/main.go
• go-peer/go.mod
• go-peer/go.sum
• js-peer/src/lib/libp2p.ts
• js-peer/.env.example

It does not include the Aleph workflow stack, deploy actions, or fork-specific operational wiring.

Validation

• go test ./... in go-peer