build(lint): throw error on JSON.stringify within a logging statement

[Hweinstock]

Problem

contributors often use JSON.stringify to get a printable form of an object in log messages, but this is hard for humans to read.

Solution

Implement a custom eslint rule that checks for instances of JSON.stringify inside of a logging statement. The implementation involves a few heuristics for catching edge cases that are explained in the comments.

In addition to implementing the lint rule, existing cases are migrated to use %O string substitution.

Within the lint message, we mention the depth limit. There is a workaround this depth limit by manually converting it to a string first with util.format: https://stackoverflow.com/questions/10729276/how-can-i-get-the-full-object-in-node-jss-console-log-rather-than-object, but seems rather involved, and uncommon enough to leave out of suggestion message.

---

License: I confirm that my contribution is made under the terms of the Apache 2.0 license.