Return all RustCrypto libs but crypto-bigint to stable versions

[fjarri]

This will make it possible for entropy-core to still use our master branch. crypto-bigint can stay at the pre-release since it is not directly exposed to the user.

[codecov]

Codecov Report

Attention: Patch coverage is 94.11765% with 3 lines in your changes missing coverage. Please review.

Project coverage is 93.13%. Comparing base (9e24b37) to head (7f9400e).

Files with missing lines	Patch %	Lines
synedrion/src/cggmp21/params.rs	90.32%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #154      +/-   ##
==========================================
- Coverage   93.16%   93.13%   -0.03%     
==========================================
  Files          43       43              
  Lines        8101     8112      +11     
==========================================
+ Hits         7547     7555       +8     
- Misses        554      557       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dvdplm]

Code LGTM.

I wonder though if core should depend on master. Aren't they better off using a tag or a branch? Right now they are using 0.2.0-beta.0 (which I think correspond to release/v0.2.0-pre.0 but I'm not actually sure) and that seems like the right thing to do.

I suggest we do this:

0. Make sure we know which tag corresponds to 0.2.0-beta.0
1. Review&merge the open PRs (or reject&close ofc)
2. Merge this PR
3. Cut a new release 0.2.0-pre.1 with (mostly) stable RC crates

[fjarri]

I guess what I meant was that we won't have to maintain two separate branches and backport changes/fixes, and entropy-core will be able to depend on the releases made on master.