These new functions are to be used when parsing the console message
which is being printed by the website under test when it used
console.log. Since these are string values that will be parsed and
reprinted to stdout, we don't necessarily need to parse a json string
into a go object (which is the main motivation for this change). This
will avoid situations where k6 browser panics and causes the test run
to end due to not being able to parse a json string.

Other areas of the implementation (e.g. toJSON or eval) still require
a go representation of the object and they will work with the existing
parse functions.

Since a string is already a string, we don't need to marshal it back to
a string. This will be used when working with console messages which
are printed by the website under test.

Work with parseConsoleRemoteObject so that the browser module avoids
trying to unmarshal objects from json to a go object. This doesn't feel
like a worthwhile operation since the string will be printed to stdout.

Work with parseConsoleRemoteObject and strings rather than any types.
The page.on API works with strings so there's no need to try to parse
a json object to a go object and then back to a js object.

Co-authored-by: İnanç Gümüş <inanc.gumus@grafana.com>

Resolves: https://github.com/grafana/xk6-browser/pull/1129/files#r1424966377

This log is notifying the user of something that can't be changed or
actioned on, so it's better represented as info rather than a warn.

This is just to clarify why these empty cases are there.

It's no longer being used.

This particular test may run slower on other machines, so accounting
for that scenario -- specifically in the CI.