Clean up after merging webcrypto & making module globally avaliable

[olegbespalov]

What?

This PR does clean-ups after merge of module and also makes crypto (and other methods) globally available

Why?

This finalizes graduation of the web crypto

Checklist

• I have performed a self-review of my code.
• I have added tests for my changes.
• I have run linter locally (make lint) and all checks pass.
• I have run tests locally (make tests) and all tests pass.
• I have commented on my code, particularly in hard-to-understand areas.

Related PR(s)/Issue(s)

#4188

Closes: #3154
Closes: #4031

[olegbespalov]

@joanlopez for the record, I've just did rebase and also adjusted texting on when the experimental import will be removed The k6/experimental/webcrypto will be removed in k6 v1.1.0

[mstoykov]

Sorry for the slow reply, but didn't have time before to finish my proof of concept for k6/timers not being done in the same way.

I did also technically went for a different way of implementing #4563 originally, but ended up being so convoluted that it made no sense. And in practice the only reason why it needed some of the stuff is so that import { setTimeout } from "k6/timers" would've been nice to have the same value as globalThis.setTimeout.

Arguably k6/timers might not need to exist, but k6/webcrypto definitely seems like it doesn't need to at all.

all that to say @olegbespalov please look at #4563 and let see if we agree on the approach of moving to js/tc55 or something like that and not actually making modules out of stuff.

[olegbespalov]

Hey @mstoykov, I've partially adopted the approach that you've used in #4563 (without actual extraction of the crypto logic) as part of this PR. So please give this PR review.