[browser] Consider DangerousAddRef for JSObject

[pavelsavara]

When we are marshaling JSObject to JS, should we DangerousAddRef on it for duration of the call ?
Our GC is scanning the stack so in most cases, that would be enough.

But there are few scenarios for which I'm not sure

• marshaling array where JSObject is item in the array
• multi-threaded stack frame which is passed between thread is allocated on a heap
• NAOT-LLVM doesn't have conservative GC

[dotnet-policy-service]

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