add troubleshoot on documentation and some lint minor refactors

[marcalexiei]

Description

Closes #3894.

I added a new section in the documentation with the step to troubleshoot error similar to the one described on #3894.

I also made two additional changes:

• I changed the error message to be more simple IMHO.
• I used RuleConfigSeverity enum to compute outcome warnings and errors.
  (The enum was already imported)

Motivation and Context

#3894

Usage examples

N/A

How Has This Been Tested?

yarn test

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[escapedcat]

Oops, would you mind rebasing this? Thanks
Thanks for your time!

[escapedcat]

Thanks! Will merge as soon as we know that v19 is doing ok

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.