Add user freeze feature

[touilleMan]

• Implementation only in memory
• Documentation is missing
• No client support

[vxgmichel]

A couple of comments, LGTM otherwise 👍

[mmmarcos]

LGTM overall. Some minor comments.

• Are you planning to add the docs from Implement RFC 1007 - Frozen users for parsec v2 #5842 to this PR?
• By "No client support" you mean the CLI?

[mmmarcos]

Is there a rationale for the "outcome" wording? (I noticed it was introduced in #6214)

I don't have strong arguments against it, it's just that it doesn't feel "standard" (which is usually better for readability). Usually this things are named result or response. Also suffix BadOutcome for enums which has the downside of using 2 words instead something like just Error.

[touilleMan]

"Outcome" comes from the outcome library, so an outcome wraps the result of a function.

Usually this things are named result or response

I think response is to be used when doing http request.

result would have been possible name, but it lacks the fact both ok and error are contained. Given in Python you expect a function to return the ok part and raise an exception for the errors, a dedicated name like outcome is good for readability.

Also suffix BadOutcome for enums which has the downside of using 2 words instead something like just Error.

This is a feature ! ^^
You have FooError which is an exception and FooBadOutcome which is an enum of possible errors.