check if newest version of package parses with fusion and if so, update packages.yml

[graciegoheen]

For each package your dbt project is using that:

• has warnings / errors
• isn't on the latest version

dbt-autofix should go check if the latest version of that package parses with fusion. Either by:

• [harder, but less burden on package maintainers] pulling down latest version and running a dbtf parse
• [easier, but 100% of package maintainers would need to update code and cut new release] checking require-dbt-version

If it does, it should update your packages.yml to use the explicit version number of the latest version of that package.

This will help folks easily upgrade to new fusion-compatible package versions as pacakge maintainers release them!

Then, we should update the warning message for that package from fusion to recommend using the dbt-autofix script. See related issue.

[jtcohen6]

Alternative idea from chatting with @akbog yesterday:

• We start running dbtf parse in hubcap CI — meaning, whenever a new package version is released, see if it's compatible with Fusion parsing
• We add "is Fusion compatibile?" to the Hub API. This would also enable us to put a nice Fusion logo on the Hub site UI, for package versions / packages whose latest version is Fusion-compatible.
• If a package has dep warnings, and the Hub API reports that a newer version of that package is Fusion-compatible, then we can include that in the warning message (strongly recommend that users upgrade) and in the autofix script (actually change packages.yml / dependencies.yml to bump to first Fusion-compatible versions)