#206 - Introduced support for custom signer

[thehenrytsai]

• Introduced new Signer interface for custom signer
• Replaced PrivateJwk with Signer in SignatureInput
• Renamed existing Signer to SignatureAlgorithm for disambiguation
• Renamed GeneralJwsSigner to GeneralJwsBuilder

[diehuxx]

A couple thoughts.

First, less pressing. In a follow up PR, we should migrate onto @web5/crypto. Thanks to @adam4leos that package has 100% test coverage. I can start on that after we get this PR merged.

Second, people are gonna have a hard time figuring out how to use a custom signer if we don't make it super clear in documentation. It's nested pretty deep in the options for <Message>#create where to pass a custom Signer. Do you mind adding a test that creates a DWN message with a custom signer just so we have it written down somewhere how to do it? We don't need the test coverage but it'll be useful to have something that we can link to. I anticipate people in Discord asking us how to use custom signers.

I'm wondering if there's a way to restructure the input to #create() methods that will make this more ergonomic or more self-documenting. Maybe flattening authorizationSignatureInput: SignatureInput into protectedHeader?: JwsHeaderParameters; customSigner?: Signer;?

Let's sync tomorrow. I've got some more thoughts based on how I see messages being created in web5-js that I can't express concisely right now.

[LiranCohen]

This looks great! The updated naming of Builder/Signer/SignatureAlgorithm definitely reads really nicely.

🎸 🚀

[thehenrytsai]

@diehuxx and @LiranCohen pushed an overhaul replacing SignatureInput with Signer directly. Tons of files are impacted, but the refactoring streamlines the code quite a lot IMO.