Default to known good version instead of latest

[marschattha]

We are now automatically updating latest version for most plugins but they might not always be compatible (may have breaking changes), so we should default to known_good instead of latest I believe

[Copilot]

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

qlty-config/src/config/plugin.rs:808

• [nitpick] Consider adding tests to verify that the new default version 'known_good' works as expected and does not introduce regressions in plugin compatibility.

"known_good".to_string()

[qltysh]

Diff Coverage for cli: The code coverage on the diff in this pull request is 100.0%.

Total Coverage for cli: This PR will decrease coverage by 0.01%.

File Coverage Changes

Path	File Coverage Δ	Indirect
qlty-cli/src/auth/auth_flow.rs	-0.5	√

🛟 Help

• Diff Coverage: Coverage for added or modified lines of code (excludes deleted files). Learn more.

• Total Coverage: Coverage for the whole repository, calculated as the sum of all File Coverage. Learn more.

• File Coverage: Covered Lines divided by Covered Lines plus Missed Lines. (Excludes non-executable lines including blank lines and comments.)

  • Indirect Changes: Changes to File Coverage for files that were not modified in this PR. Learn more.

[brynary]

@marschattha yes, this seems like the right way to go. Do we have any gaps as in plugins where we don't have automated updates?

[marschattha]

Yes there are a few, Radarlint plugins, Rust plugins (since they come packaged with rust) and Go plugins.

List of covered: Github, Ruby, Python, Php, Node and Runnable Archive/Java.