JWT Support

[GrantErickson]

Don't merge this, just for diffs and comments

[meghanmae]

Question for Andrew: Does the information on Identity User get exposed to the client via coalesce? (e.g. the password hash?)

Is this the best way to hide it?

    [InternalUse]
    public override string? PasswordHash { get; set; }

[ascott18]

The answer lies in the generated DTOs, and it is "yes".

And yes.

[ascott18]

Is the exact goal here to add JWT bearer tokens as the authentication scheme? This could be substantially simpler if opaque bearer tokens or cookies are suitable. https://learn.microsoft.com/en-us/aspnet/core/security/authentication/identity-api-authorization. You could delete the controller, and most of the configuration in Program.cs

In terms of presenting this in the format of the show, I think this is 3 episodes?

1. Adding swagger. Including adding IntelliTect.Coalesce.Swashbuckle - https://github.com/IntelliTect/Coalesce/blob/dev/playground/Coalesce.Web.Vue3/Program.cs#L63
2. Adding Identity data models, interacting with them via Coalesce (adding/removing roles from users maybe?)
3. Adding authentication and authorization (sign in, accessing a role-restricted action)