Update version output and logic

[stu-k]

resolves #4724

Description

Most notably, updated the logic for displaying plugin information as follows:

• If the plugin has neither the same major nor the same minor as the installed core version, it is considered incompatible
• Then, if the latest version of the plugin can not be found, a "no version available" message will be displayed
• Then, the plugin is compared with its latest version to display an appropriate message based on if it is ahead, matches, is behind the latest version

The tests capture the intended code paths, please review them for more information about outputs.

Checklist

• I have signed the CLA
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• I have added information about my change to be included in the CHANGELOG.

[github-actions]

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.

[jtcohen6]

Nice work @stu-k, this represents a meaningful improvement and refactor of the code! I left a handful of comments. Only one is a true blocker (Major.Minor compatibility comparison). The rest are smaller + cosmetic only.

There's one bigger question about the right way to present upgrade info when it's relevant to core + many plugins. I think it would be worth a more generic message that prints https://docs.getdbt.com/dbt-cli/install/overview once, rather than once for each.

[ChenyuLInx]

This looks great! Very solid refactor of the code! Left one nitpick that's only my personal preference. Can also leave it out if you feel like the current way is easier to read!

[ChenyuLInx]

Looks like there's a mypy error, otherwise looks good!

[stu-k]

@ChenyuLInx That error doesn't have to do with anything I added or changed.
The same line exists on main https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/config/project.py#L194

EDIT: Whoops totally caused by my changes.

[ChenyuLInx]

@ChenyuLInx That error doesn't have to do with anything I added or changed.
The same line exists on main https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/config/project.py#L194

Yes, looks like this line is not even touched. I am not sure why mypy complains about it either. But when I run mypy on main it doesn't have any error. We will have to fix it or ignore this to get the workflow pass