[wasm] avoid eval, design better API for InvokeJS

[pavelsavara]

After change #61212 Rollup started producing warning about eval.

(!) Use of eval is strongly discouraged
  https://rollupjs.org/guide/en/#avoiding-eval
  method-calls.ts

We could suppress it globally, but it's not ideal.

{
  onwarn(warning, warn) {
    if (warning.code === 'EVAL') return
    warn(warning)
  }
}

As @lewing suggested, we should consider deprecating the method, since it's only internal API.

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

After change #61212 Rollup started producing warning about eval.

(!) Use of eval is strongly discouraged
  https://rollupjs.org/guide/en/#avoiding-eval
  method-calls.ts

We could suppress it globally, but it's not ideal.

{
  onwarn(warning, warn) {
    if (warning.code === 'EVAL') return
    warn(warning)
  }
}

As @lewing suggested, we should consider deprecating the method, since it's only internal API.

Author:	pavelsavara
Assignees:	pavelsavara, maraf
Labels:	arch-wasm, area-System.Runtime.InteropServices.JavaScript
Milestone:	7.0.0

[pavelsavara]

@kg said in chat:
"maybe we solve it with source generators and then you can invoke that with the new invoke api
use an icall to register each invokejs blob at startup
and then those have unique ids you use to invoke them
that would let us use new Function since it's once"

[ilonatommy]

@pavelsavara, @maraf, have you tried using the idea with new API? Any thought on that?

[pavelsavara]

This is related to CSP and I think we would be able to at least reduce it.