Fix multiple linter support (#2571)

[nullie]

For #2571

• Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
• Title summarizes what is changing
• Has a news entry file (remember to thank yourself!)
• Unit tests & system/integration tests are added/updated
• Test plan is updated as appropriate
• package-lock.json has been regenerated by running npm install (if dependencies have changed)

[msftclas]

All CLA requirements met.

[d3r3kk]

Thanks for the PR @nullie, and the mention @iansan5653. Looking at your work now.

[d3r3kk]

Seems good but we have some unrelated failures in tests at the moment. I'm going to add some code to quell those for the moment...

[d3r3kk]

Looks fine, and fixes the issue at hand. Thanks @nullie!

[d3r3kk]

Taking the fix as it does address the runtime problem.

However, it also re-enables a flaky test that has been pushed to a high priority item for our team this sprint.

[nullie]

That was quick, I've actually made some mistakes in this and want to correct and refactor

[iansan5653]

He acted quickly because your PR addressed a really widespread problem (#3700). Probably should just submit another PR with revisions