Upstream wreq 0.11.3 ships the KeyShare registration fix (PR #582) that
blocked us on 0.11. This bump adopts the v0.11 API renames:

- Client kwarg: verify -> tls_verify (silently dropped pre-rename;
  badssl confirmed our CertStore would have been a no-op)
- TlsOptions: key_shares_limit=int -> key_shares=Sequence[KeyShare]
- repr(Emulation.ChromeX) now returns "Profile.ChromeX" (ClassVar
  restructure), so the three hardcoded repr assertions in test_browser
  were updated

Picks up Chrome146/147 emulation profiles; DEFAULT_EMULATION advances
to Chrome147. Build numbers 146:(7680,31) and 147:(7727,24) added to
_CHROME_BUILDS (versionhistory.googleapis.com first-stable releases).

Safari + Dart fingerprints re-verified against tls.peet.ws after the
BoringSSL bump; JA3/JA4/H2 hashes unchanged. Chrome147 wire-tested vs
nowsecure.nl (CF max-security) -200 on first try, no challenge.

Docs note the Client-level silent-acceptance footgun (extends prior
TlsOptions/Http2Options note) and the repr() shape change.