isSupportedBy
Whether a session with method on this suite runs on crypto where it is: the suite is implemented and fits the method (EdhocMethod.isCompatibleWith), and the backend supports
the ephemeral key exchange: key agreement on the curve, which static-DH authentication uses too (RFC 9528 §4.1.1), or the KEM (draft-ietf-lake-pqsuites §3);
the signature algorithm, if either side of method signs (RFC 9528 §5.3.2);
the EDHOC and application AEADs, and the EDHOC and application hashes with HMAC for SHA-2 (RFC 9528 §3.6, Appendix A.1).
Platforms differ (WebCrypto has no ChaCha20/Poly1305, so suites 4 and 5 do not run there). EdhocInitiator and EdhocResponder offer and accept only the suites for which this is true, and it is true exactly when a handshake between them on this backend succeeds. Each call asks CryptoBackend.supports up to six questions. DefaultCryptoBackend answers them from memory after the first time, but a backend that keeps the probing defaults runs a probe for each, so call this once per backend rather than per session; the state machines remember the answers in their configuration (docs/adr/0001-crypto-capabilities.md).