[FEATURE] JSON5 support for integration config files

[Swiddis]

Is your feature request related to a problem?
JSON5 is an extension of JSON that makes it easier for humans to work with, for scenarios like config files. Among other things this includes:

• Comments
• No need to quote keys
• Multiline strings
• Trailing comma support

Integrations currently uses JSON to store all of its config data, which isn't terrible but also isn't ideal.

What solution would you like?
It would be nice to support JSON5 for integration config files, since these are typically written by hand by integration developers.

What alternatives have you considered?
We could use alternative formats like TOML or YAML, but that seems like a more drastic change. It probably wouldn't be a massive migration since we could have backwards-compatible JSON support, but it would be more complex and require maintaining both serializations. JSON5 is a more drop-in replacement that still has some nice ease-of-use additions.

Do you have any additional context?
Marking this as "Good First Issue" since most of the work is replacing the import in the Integration file reader and Integration JSON reader, give or take some more CTRL+F for JSON.parse refs.

[devesh-2002]

May I take up this issue?

[Swiddis]

By all means! Feel free to ask any questions here as well.

[Swiddis]

Completed by #1732