Find TLS protocol configuration in properties and YAML

Inventories Spring Boot configuration files that set an embedded server's TLS protocol floor or cipher suites — server.ssl.enabled-protocols, server.ssl.protocol and server.ssl.ciphers, plus any key named in additionalPropertyKeys — and classifies each value by whether TLS 1.3, and therefore JEP 527 hybrid key exchange, remains reachable. A pinned server.ssl.ciphers list with no RFC 8446 suite blocks TLS 1.3 even when the protocol floor allows it. Rows land in the same TLS configuration inventory data table as the Java surface. Keys are matched with relaxed binding, so enabled-protocols, enabledProtocols and ENABLED_PROTOCOLS all match; values may be a single token, a comma-separated string, or a YAML sequence in either flow or block style. Configuration a source scan cannot see — config servers, ConfigMap overlays, environment variables — is out of scope, so an absent row is not evidence of a modern floor.