WebCrypto types need to be cleaned up

[vlovich]

Opening this to track this work but the fixes should live in the internal Cloudflare runtime code (either as code changes or overrides). The various operations are too generic. For example, we should export a AesGcmParams that has a fixed name of AES-GCM whereas currently we have a catch-all SubtleCryptoEncryptAlgorithm that is the union of all possible values. Same for things like SubtleCryptoImportKeyAlgorithm, SubtleCryptoHashAlgorithm which don't technically exist. As a nicety, we should hard-code the set of legal values for params that only have a valid set.

[vlovich]

cc @harrishancock for visibility.

[mrbbot]

Hey! 👋 We'll get this fixed in the next major version of workers-types using the new type generation system. 👍

[mrbbot]

As a quick update, this is still an issue with @cloudflare/workers-types@4. This is something we can potentially investigate fixing when we migrate type generation to a Worker. 👍