WIP: Wifi aware mesh

[callebtc]

Description

Checklist

• I have read the contribution guidelines: https://github.com/permissionlesstech/bitchat-android?tab=readme-ov-file#contributing
• I have performed a self-review of my code

• I have mentioned the corresponding issue and the relevant keyword (e.g., "Closes: #xy") in the description (see https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)
• If it is a core feature, I have added automated tests

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Avoid binding process to Wi‑Fi Aware network

When acting as the Wi‑Fi Aware server, onAvailable calls cm.bindProcessToNetwork(network). This sets the process‑wide default network to the peer’s Aware link, so while a connection is active all outbound traffic (e.g., Nostr relay connections or HTTP calls) will be forced over a local, non‑routable network until the session drops. The client path explicitly avoids process binding, so this likely isn’t intended. Consider binding only the server socket (e.g., via network.bindSocket or the network’s socket factory) instead of switching the entire app to the Aware network.

Useful? React with 👍 / 👎.