sandlock-oci: wire networking and HTTP ACL from io.sandlock.<section>.<field> annotations

[congwang-mk]

The OCI runtime spec has no native fields for outbound network policy or HTTP ACL configuration, so sandlock-oci now reads them from reverse-DNS annotations in config.json, following the convention other runtimes use (io.katacontainers., dev.gvisor., run.oci.*):

• io.sandlock.network.allow / .deny: outbound destination rules
• io.sandlock.network.allow_bind / .deny_bind: bind port rules
• io.sandlock.network.port_remap: transparent port remapping, default on so container servers can bind (set "false" to opt out)
• io.sandlock.http.allow / .deny / .ports: HTTP ACL rules and intercepted ports
• io.sandlock.config.http_ca / .http_key / .http_ca_out: host-side MITM CA material, resolved relative to the bundle
• io.sandlock.config.http_inject_ca: sandbox-virtual trust bundles to splice the CA into

Multi-value annotations use ; as the separator since , is significant inside net specs (github.com:22,443) and HTTP rules contain spaces. Each option is a no-op when its annotation is absent; malformed http.ports entries fail at spec parse time, and mismatched CA/key pairs fail at sandbox build time.

🤖 Generated with Claude Code