Report usage of the crypto

[olegbespalov]

What?

We've made the webcrypto available as crypto globally in #4278. The way how we report module statistics excludes it, but for us, it's still good to know what's the usage which could help us understand if we should invest more into the development.

@mstoykov made a solid statement that we might not need statistics because WebCrypto API is a standard, so we should invest in it regardless, that's why it's worth firstly trying to find consensus if this task makes sense at all. But for now, I'm just documenting this fact of excluding from reports.

As the potential way of doing that could be

k6/internal/js/bundle.go

Lines 403 to 413 in 1e9994c

	globalThis := rt.GlobalObject()
	err = globalThis.DefineAccessorProperty("global",
	rt.ToValue(func() sobek.Value {
	if err := b.preInitState.Usage.Uint64("usage/global", 1); err != nil {
	b.preInitState.Logger.WithError(err).Warn("couldn't report usage")
	}
	return globalThis
	}), rt.ToValue(func(newGlobal *sobek.Object) { // probably not a thing that will happen but still
	globalThis = newGlobal
	}),
	sobek.FLAG_TRUE, sobek.FLAG_TRUE)

Why?

Even the crypto (WebCrypto API) is a standard it doesn't look so far from the other k6's modules and having numbers along with the others to make a future decisions might be a good idea.