Tracking issue for generic (e.g. key) types and owned/ref aliases

In the latest release of spki it was changed to have generic AlgorithmIdentifier and SubjectPublicKeyInfo, along with *Owned and *Ref type aliases. This allows either zero-copy decoding with a lifetime, or decoding to an owned type with no lifetime (which enables e.g. on-the-fly 1-pass PEM decoding, since you can't borrow bytes from a PEM input).

However, other crates in this repo didn't receive a similar treatment. This is a tracking issue for those.

• pkcs1
  • OtherPrimeInfo
  • RsaOaepParams
  • RsaPrivateKey
  • RsaPssParams
  • RsaPublicKey
• pkcs5 https://github.com/RustCrypto/formats/pull/1195
  • pbes2::kdf::Kdf
  • pbes2::EncryptionScheme
  • pbes2::Parameters
  • EncryptionScheme
• pkcs8 https://github.com/RustCrypto/formats/pull/1483
  • PrivateKeyInfo
  • EncryptedPrivateKeyInfo
• sec1
  • EcPrivateKey

Start by examining the generic AlgorithmIdentifier and SubjectPublicKeyInfo treatment in spki, then review the unchecked types listed under pkcs1 and sec1. Done means the remaining listed types support the corresponding generic and *Owned/*Ref treatment, with the tracking checklist updated.