fix(permissions): match network rules against the resource host

[Scorpion197]

Fixes #1884.

• Network rule patterns written in the documented host form (api.example.com, api.example.com:443, *.example.com, *) never matched, because the kernel checks the URI form of the resource (tcp://host:port, dns://host) and a single * cannot cross the //. A documented allowlist therefore denied every host, and a documented blocklist permitted every host.
• Scheme-less network patterns are now matched against the host subject of the resource: the bare host, and host:port when a port is present. Patterns that carry a scheme (tcp://..., dns://...) keep matching the full URI, so existing policies written in that form are unchanged.
• Resources that do not parse as scheme://subject are only matched by full-URI patterns, so unexpected resource shapes fail closed. Other pattern scopes are untouched.
• Adds crates/native-sidecar-core/tests/network_permissions.rs covering the matrix from the report in both directions, the URI form, IPv6 literals, last-rule-wins, the post-resolution evaluator, and the fail-closed cases. Existing tests that fed bare host:port resources into the network evaluator now use the tcp:// form the kernel actually produces.
• Documents the host and URI pattern forms in permissions.mdx. The shipped allow-one-host example is unchanged and now works.

This is the matcher alternative offered in #1910, which corrects the docs to the URI form instead. The TypeScript merge-over-default behavior described in the second half of #1884 is a separate layer and is not addressed here.