feat: add ES512 algorithm support using P-521 elliptic curve

[arsenin-kitsoft]

Suggested changes for #250

Replacement for #478 with updated dependencies.

[arsenin-kitsoft]

@Keats @arckoor Local tests are green for both feature sets, but there are extensive dep bumps beyond p* libs. Please advise if this is okay. Specifically questionable is the bump of rsa to an rc version of 0.10 (the other libs have dragged it).

[arckoor]

rc versions are a no
is there no path at all in the deps to upgrade just p521? I assume it pulls a newer rand which is then too new for rsa?

[arckoor]

Why not adjust the macro? We just discard the recovery ID do we not?

[arsenin-kitsoft]

Yeah, that was easy 😅

[arsenin-kitsoft]

@arckoor Eeh, there's a dep mess with P* 0.14 and not only with the 521 one 🤔
Should we wait for rc to release?
Because I don't think I'm equipped to untangle this one 😿

[atezet]

Yeah, the rsa rc is very annoying. I think it should be possible to upgrade just the pxxx ones, but not just p521

[arsenin-kitsoft]

Had to bump getrandom to 0.4 as well to clear the wasm tests.

[arsenin-kitsoft]

@atezet didn't work for me, unfortunately - still breaks with dep clash.

[arsenin-kitsoft]

RustCrypto/RSA#647 rsa 0.10 release track

[arckoor]

That's very unfortunate. I can still fully review this if you'd like, or we can pick it up once all the dependencies are sorted out

[arsenin-kitsoft]

@arckoor I've addressed the issues with tests and with macros that you've highlighted above. But I think it's better to wait for the next release of RSA.

[atezet]

I briefly looked at it and if I'm not mistaken there's a dependency clash on signature::{Signer, Verifier}, right? Why are these traits necessary even if the aws_lc_rs backend is used? Or is the problem also with getrandom and wasm?