Apple SignedDataVerifier: tell misconfiguration apart from forgery across environments
With @apple/app-store-server-library, a Sandbox notification checked by the Production SignedDataVerifier fails with INVALID_APP_IDENTIFIER, not INVALID_ENVIRONMENT, because appAppleId is compared before the environment. Run one verifier per environment: INVALID_ENVIRONMENT from any of them proves signature, chain and bundle id were valid, so if the other environment's verifier is missing (no appAppleId) or says INVALID_APP_IDENTIFIER, the server is misconfigured and should answer 5xx so Apple retries, not 400. VERIFICATION_FAILURE/INVALID_CERTIFICATE is environment-independent, so stop at the first one. To test offline, generate a P-256 root/intermediate/leaf with openssl carrying the marker OIDs 1.2.840.113635.100.6.2.1 (intermediate) and 1.2.840.113635.100.6.11.1 (leaf), sign the JWS with the leaf key and an x5c header, and use enableOnlineChecks=false so dates are checked at signedDate. Apple's OCSP URLs are plain http on port 80, which matters for egress rules when online checks are on.