only report dependencies from project files that have a target framework

[brettfo]

If a <TargetFramework> cannot be parsed from a .csproj/.vbproj/.fsproj, there's no meaningful update that can be performed, so we explicitly check for that. This also means that we can't pull dependencies directly from packages.config, etc. because we still depend on the project file's contents, so the tests were updated to reflect that. global.json and dotnet-tools.json are exceptions to requiring a project file and are still handled appropriately.

Update to smoke-tests

This PR depends on a PR dependabot/smoke-tests#197 and they must be taken in parallel.

Temporary commit has been removed. N.b., this PR has a temporary commit that points to the smoke-tests PR branch to show the smoke-tests passing. That commit will need to be removed before this is merged.

[brettfo]

Smoke tests are failing for expected reasons, going to start on those now. The short version is that a dependency is now only reported for its initiating .csproj where before it was reported for the .csproj as well as Directory.Packages.props, etc.

[brettfo]

Edit: My smoke-test changes were out-of-date. I've updated that branch so this shouldn't be an issue any more.

Original comment:

The failing smoke test is unrelated to this PR. Error message/diff looks like:

--- smoke.yaml
+++ result.yaml
@@ -100,7 +97,7 @@
                   support_file: false
                   type: file
                 - content: |
-                    # This file is automatically @generated by Poetry 1.7.1 and should not be changed by hand.
+                    # This file is automatically @generated by Poetry 1.8.2 and should not be changed by hand.