GenerateKeyPseudoCode.md is inconsistent about parameter sizes

[KalleOlaviNiemitalo]

Provider data

CaskSecret.md says the provider data can be up to 40 characters:

cask/docs/CaskSecret.md

Lines 43 to 48 in 6f4c272

	<provider-data-size> ::= 'A'..'K' ; 'A' = zero 3-byte optional data segments, 'B' = one optional 3-byte
	; segment, up to a maximum of 'K' = 10 optional 3-byte data segments.
	<provider-kind> ::= <base64url> ; Provider-defined key kind.
	<provider-signature> ::= 4 * <base64url> ; Provider identifier (24 bits).
	<provider-data> ::= { <24-bits> } ; 0 - 10 four-character (24-bit) segments of provider data. The
	; count of segments is encoded in the <provider-data-size> field.

GenerateKeyPseudoCode.md however says it cannot be more than 12 characters:

cask/docs/GenerateKeyPseudoCode.md

Line 19 in 6f4c272

- Provider data (if non-empty) has a length that is a multiple of 4 characters and no more than 12 characters.

even though another part of GenerateKeyPseudoCode.md allows 10 segments of 4 characters each:

cask/docs/GenerateKeyPseudoCode.md

Line 41 in 6f4c272

- O = base64url-encoding of optional data size, a count of 3-byte segments, one of 'A' (0 segments) - 'K' (10 segments).

Sensitive data

CaskSecret.md allows only 256 or 512 bits of sensitive data:

cask/docs/CaskSecret.md

Line 42 in 6f4c272

<sensitive-data-size> ::= 'B' | 'C' ; 'B' = 256-bit sensitive data size, 'C' = 512-bit.

GenerateKeyPseudoCode.md however allows 128, 256, 384, or 512 bits during validation:

cask/docs/GenerateKeyPseudoCode.md

Line 21 in 6f4c272

- Secret data size is between 1 (a single 16-byte segment of sensitive data = 128 bits) and 4 (four 16-byte segments = 512 bits).

even though another part of GenerateKeyPseudoCode.md allows only 256 or 512 bits:

cask/docs/GenerateKeyPseudoCode.md

Line 40 in 6f4c272

- S = base64url-encoding of secret data size, 'B' (256 bits) or 'C' (512 bits).