Implement formatter similar to JSCS default reporter

The default JSCS reporter includes the context of the code and an indicator to the specific character which is causing the violation. With JSCS joining ESLint, that’s the one JSCS feature I’d miss (and love to see added to ESLint).

As an example, it can look something like this:

All identifiers must be camelCase or UPPER_CASE at C:\inetpub\wwwroot\site.local\JavaScript\BaseLocator.js :
    66 |        this._noLocationSpan = value;
    67 |    },
    68 |    get_instructionSpan: function() {
------------^
    69 |        return this._instructionSpan;
    70 |    },

[ilyavolodin]

@vitorbal 👍 on proposed enhancements

[qfox]

Would be great to have line and column in the filename link to use cmd+click behaviour