feat: add lumos crypto.randomBytes to replace node's

[twhy]

Description

1. Add ckb-lumos/crypto package which has a randomBytes method to replace node crypto.randomBytes.
2. export ckb-lumos/crypto in ckb-lumos/lumos

Type of change

• New feature (non-breaking change which adds functionality)
• Refactor (non-breaking change)

How Has This Been Tested?

Unit tests

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
lumos-website	✅ Ready (Inspect)	Visit Preview	Jun 6, 2024 6:09am

[codecov]

Codecov Report

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

Project coverage is 87.06%. Comparing base (8d11c75) to head (57977b8).

Additional details and impacted files

@@             Coverage Diff             @@
##           develop     #701      +/-   ##
===========================================
+ Coverage    85.67%   87.06%   +1.38%     
===========================================
  Files          131      132       +1     
  Lines        25247    25246       -1     
  Branches      2663     2738      +75     
===========================================
+ Hits         21631    21981     +350     
+ Misses        3576     3225     -351     
  Partials        40       40              

Files	Coverage Δ
packages/crypto/src/index.ts	100.00% <100.00%> (ø)
packages/debugger/src/context.ts	92.51% <100.00%> (-0.04%)	⬇️
packages/debugger/src/executor.ts	97.93% <100.00%> (+0.02%)	⬆️
packages/hd/src/keystore.ts	91.69% <100.00%> (+0.06%)	⬆️
packages/hd/src/mnemonic/index.ts	34.97% <75.00%> (+0.21%)	⬆️

... and 8 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8d11c75...57977b8. Read the comment docs.

[twhy]

@homura Can this PR be merged into develop ?

[homura]

Can this PR be merged into develop ?

Not yet. We'll publish 0.23 first

[twhy]

Can this PR be merged into develop ?

Not yet. We'll publish 0.23 first

Let's merge this and move forward.

[homura]

Let's merge this and move forward.

Maybe it's better to target this PR to the 'browser-compatibility' branch first until the node modules, such as 'buffer' and 'crypto', are fully dropped. Then, check if it works properly with Vite, CRA, and Next.js.

[twhy]

The plan is to replace Node crypto first, then replace Buffer with Uint8Array

Now the first PR is done, and it's safe to merge it. The second is ready locally.

metioned in #645

[twhy]

Let's merge this and move forward.

Maybe it's better to target this PR to the 'browser-compatibility' branch first until the node modules, such as 'buffer' and 'crypto', are fully dropped. Then, check if it works properly with Vite, CRA, and Next.js.

I will merge this PR into a newly created branch browser first.