console.log should not call object methods

從 Android runtime 的 console.log 物件格式化入口開始，重現提供的 TypeScript 程式碼片段，包括失敗的 toJSON 範例。將輸出與 issue 中描述的 Chrome 行為進行比較；當記錄不會呼叫物件方法，也不會在其中一個方法拋出例外時中止，即表示完成。

Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):

• CLI: 8.1.5
• Cross-platform modules: 6.5.11
• Android Runtime: 6.5.3
• iOS Runtime (if applicable): Possibly irrelevant
• Plugin(s): Possibly irrelevant

Describe the bug
When an object contains a toString or toJSON method, and you print that object through console.log, it will automatically call that function. This is very different from what Chrome console.log does and may cause confusing behavior. For example:
The NativeScript HTTP client returns an object with a property called content that contains an object with a to toJSON method, when you console.log the return object, it will automatically call that toJSON method, while it might not even be JSON, causing the console.log to fail with a weird error from JSON.parse, like Unexpected end of JSON input.

To Reproduce

const randomVar = "test123";
const obj = {
	toJSON: () => "toJSON => this should not be logged " + randomVar
};

console.log(obj);

Expected behavior
I think it should print something like:

{
  "toJSON": ƒ
}

Or, it should catch any errors that happen during the format, and then fall back to it's normal behavior (going to toString, or not printing the property at all). It should not be breaking off the whole console.log and return the exception.

Additional context
Output when doing something like this in Chrome:

Output when doing something like this in NS:

When causing an error inside the function with:

const obj = {
	toJSON: () => JSON.parse("fakejson")
};

console.log(obj);

In Chrome:

In NS: