feat: custom json linter

[twinguy]

This PR addresses: #80

• Added new make targets (build-iota-linter, run-iota-linter and clean-iota-linter)
• Updated .golangci.yml with linter specific configs
• Updated CI pipeline to run custom linter
• Added docs for linter usage

Failed Github Action run (Showing linter findings)
Successful Github Action run (Excluded modules folder in .golangci.yml)

[twinguy]

@diyor28 Couple of notes on this PR. I initially attempted to package and deliver this as a golangci custom plugin but kept struggling with use their plugin architecture. I finally settled on simply building and running the linter using make targets which feels more straightforward. As always, feedback welcome.

[diyor28]

That's fine, as long as we add an issue to the backlog to later come back to this and make a golangci-lint plugin

[diyor28]

Is this supposed to be the line number after the semi column?

[twinguy]

Yes, line number is provided by the code analyzer framework unless the entire JSON structure is invalid which it then hard codes to a value of 1.