Release v22.70.0

Changed

• The Screenplay generator now targets Cratis.Screenplay 4.135.0 (NuGet and npm).
• An encryption scope other than the default is kept. A concept marked [Encrypted(EncryptionScope.Namespace)] or [Encrypted(EncryptionScope.Global)] together with [NotAudited] is written as secret scope namespace|global when authoring-only constructs are enabled. In the default executable output it stays a bare secret, and the new SP0061 diagnostic names the scope the document does not state. (#3089)
• [PII] on a property whose type is not a concept (for example [PII] string Email) is now reported with SP0062 instead of being dropped silently. Screenplay classifies concepts, so introduce a personal-data concept to carry the marking. (#3089)
• When [PII] on one property promotes its concept to pii everywhere, the new SP0063 diagnostic names the other uses of that concept that were not marked. (#3089)
• The SP0058 and SP0059 messages and the compliance section of the generator documentation now use the current pii and secret terms. (#3089)
• Generator verification tolerates a known Screenplay admission-limit diagnostic only when the loaded Screenplay compiler still lists its code as an active error, so a retired or downgraded code fails verification instead of being silently accepted. (#3099)