Fix Node Crypto polyfill

[g12i]

What?

Allow overwriting the global.crypto property when polyfilling it.

Why?

#48941 introduced global.crypto polyfill. The problem is that if some library (e.g. xksuid) tries to do the same thing, it breaks as global.crypto is defined as non-writable¹. Arguably libraries should check for global.crypto presence before overwriting it BUT I think polyfill should match the actual implementation².

How?

Make global.crypto enumerable and configurable, as well as define set implementation³.

Footnotes

1. ↩

2. ↩

3. ↩

[timneutkens]

Can you add tests for this change?

[g12i]

Hey @timneutkens, of course! I added unit tests. I think I might have not pushed them by the time I pressed Create PR button. Would you think more tests are needed?

[timneutkens]

Looks good to me now 👍 thanks!