Exit bandwidth metadata uses netstack proxy on single-tun wireguard

[tommyv1987]

• Single-tun wireguard (iOS and Android netstack) routes exit bandwidth metadata through the same local TCP proxy as entry, instead of binding HTTP to the utun interface name.
• Removes the immediate broken exit metadata dispatch that caused bandwidth check failures, tunnel shutdown, and roughly 13-second auto-reconnect loops after connect.

Ticket

JIRA-NYM-XXXX

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.

Checklist:

• Changelog

Screenshots (optional, if UI related)

---

This change is 

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0e9e49e1-d93d-4412-a064-c1e0f3785280

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/core-exit-bandwidth-metadata-netstack

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[neacsu]

I don't think this change is correct, the endpoints were queried correctly before.