Linting: Update broken link in knowledge check

[Mafzii]

Because

Clicking "Which problems can linting prevent?" would open page that does not exist anymore, causing a 404. Added a different link that provides answers about the link description and is from a trusted source.

This PR

• Changed https://mikecavaliere.com/javascript-linting-what-developers-need-to-know/ to https://www.sonarsource.com/learn/why-linter/#:~:text=Linting%20tools%20offer%20a%20crucial,issues%20ever%20turning%20into%20bugs

Issue

Contributing doc said no issue needs to be made for a small fix

Additional Information

If there is any better link to include instead of the one added comment it below

Pull Request Requirements

• I have thoroughly read and understand The Odin Project curriculum contributing guide
• The title of this PR follows the location of change: brief description of change format, e.g. Intro to HTML and CSS lesson: Fix link text
• The Because section summarizes the reason for this PR
• The This PR section has a bullet point list describing the changes in this PR
• If this PR addresses an open issue, it is linked in the Issue section
• If any lesson files are included in this PR, they have been previewed with the Markdown preview tool to ensure it is formatted correctly
• If any lesson files are included in this PR, they follow the Layout Style Guide

[Mafzii]

@MaoShizhong it seems like someone else's PR was accepted even though it was made after mine. Maybe add a label for PRs that are not attached to an issue so that its easier to see duplicates of these small fixes? Also should I close this PR now that its outdated?

[MaoShizhong]

@MaoShizhong it seems like someone else's PR was accepted even though it was made after mine. Maybe add a label for PRs that are not attached to an issue so that its easier to see duplicates of these small fixes? Also should I close this PR now that its outdated?

PRs that are linked to close issues do have a symbol on them in the PR list (so if it doesn't have it, it's not linked to close an open issue):

What happened here though was just 100% my own mistake. I check open issues and PRs for this before reviewing, but I just straight up completely missed this PR, which is why I approved the later one. So that's entirely on me and I apologise for this.

In this instance, we can close this PR because an appropriate change has already been made for the issue raised by this PR. Again, my apologies. We would typically catch duplicates when we check things.
I'm sure there will be more contribution opps available though, so do keep an eye out! And thank you for opening this PR as well.