Clarify the supported signature algorithms for certificates

[sleevi]

Separate from #277, the support for signature algorithms currently states:

openscreenprotocol/index.bs

Lines 367 to 370 in 5488c7b

	* Supporting the at least one of the following signature algorithms:
	* secp256r1_sha256
	* secp384r1_sha384
	* secp521r1_sha512

However, this is not a defined X.509/PKIX signature algorithm. It's likely these names were derived from RFC 8446, Section 4.2.3's SignatureScheme registry, but those don't directly translate here.

Further, experience has shown that implementors who have attempted to implement ECDSA within certificates have, at times, incorrectly encoded the subjectPublicKeyInfo/signatureAlgorithm, through incorrect interpretation of the algorithm parameters, or through novel (problematic) attempts at representing the curve.

In more modern certificate profiles, an effort has been made to explicitly specify the encoded byte representation, namely:

• secp256r1_sha256 = 301306072a8648ce3d020106082a8648ce3d030107 for the public key AlgorithmIdentifier, 300a06082a8648ce3d040302 for the signature AlgorithmIdentifier
• secp384r1_sha384 = 301006072a8648ce3d020106052b81040022 for the public key AlgorithmIdentifier, 300a06082a8648ce3d040303 for the signature AlgorithmIdentifier

[markafoltz]

Closed by #288.