Andrew Hauck

Reject ambiguous authorities on ingress and egress

Add snapshot readiness for selectors

Use u32 internal indices in LRU linked list

Represent the raw request-target as a single value

Refactor LB race shutdown

Update default error_while_proxy retry conditions

Reapply "Acknowledge downstream h2 RST_STREAM while the upstream request-body write is blocked."

Add RST_STREAM cancellation test on idle streams

Split request-target classification into pingora-http pingora-http needs to locate the path component of a request-target, and pingora-core needs to locate the authority in those same bytes to reconcile it against `Host`. Two parsers reading one target with their own idea of where the authority ends can be made to disagree, so there should only be one. Move the classifier into `pingora_http::authority`: `raw_target_authority`, `RawTargetAuthority`, and `is_http_family_scheme`. It reads raw bytes, requires no imports at all, and has no transport or runtime dependencies. The policy that acts on a classification stays with its callers. `validate_request_authority`, the CONNECT `Host` reconciliation, and the shared ingress field checks remain in pingora-core, where `validate_request_authority_fields` keeps its `pub(super)` visibility. `has_ambiguous_port_suffix` stays there too: it judges an authority that has already been located rather than locating one, and every caller is a pingora-core consistency check, so moving it would export an item with no user on the other side of the boundary. Validation stays explicit rather than an invariant enforced by `RequestHeader::build`, because custom protocols intentionally permit nonstandard authority relationships. This widens the public API of pingora-http by three items. `raw_target_authority` and `RawTargetAuthority` were already public in pingora-core; `is_http_family_scheme` was private and gains a doc comment describing the normalization rules that make a scheme's membership in that set change where the authority ends. Moving only the classifier is what keeps the policy helpers unexported, so nothing needs to be hidden from rustdoc to stay out of the stable surface. pingora-core re-exports the classifier, so existing import paths continue to work unchanged. No behavior change.

Fix racy closes_only_unclaimed_fds tests