Remove Goja from Execution Context Eval and from related parts

[inancgumus]

What?

All of these changes are forced by the compiler and tests while working on ExecutionContext.Eval.

• We can now use CDP/JS values without involving Goja.
• Removes Goja from ExecutionContext. After this refactoring, everything started to fall apart, and we needed to refactor many parts of the code together. I couldn't split the second commit into smaller commits because it would break the build.
• Removes Goja handling from most of the common types.
• After this change, Goja can no longer do the conversion. So we add a generic convert helper to convert any values to type-safe values. There is another one in the test browser as a helper for the tests.

Note

These additional PRs are created that will merge into this one.

• Add goja escape assertions #1191
• Fix goja escape from DispatchEvents #1193
• The rest are in Remove Sobek from Execution Context Eval #1182.

Why?

• See Sobek runtime shouldn't be accessed while parsing options in async APIs #1162.
• See Remove Sobek from Execution Context Eval #1182.
• Using native Go constructs instead of depending on Goja transformations.

Checklist

• I have performed a self-review of my code
• I have added tests for my changes
• I have commented on my code, particularly in hard-to-understand areas (not sure about this one. I added TODOs for future PR work, like returning errors)

Related PR(s)/Issue(s)

Updates: #1182, #1170

[ankur22]

This feels like a pretty big step forward into moving away from working with goja within the core business logic 👏

I've left comments for you to review, but I need to review it some more.

[ankur22]

Great work. The code is easier to read without all that goja back-and-forth type transformation.

[ankur22]

LGTM 🚀