Inconsistent framework specification stops NuGet updating tools like "dotnet-outdated" from being able to detect update

[mgroetan]

When using the "dotnet-outdated" tool to scan for possible NuGet updates, it fails to do so for the "Microsoft.VisualStudio.Azure.Containers.Tools.Targets" package.
It can successfully download a list of versions with a NuGet feed client, but when filtering for applicable frameworks, it yields nothing.

The reason for this seems to be that the package reports only supporting .NET Framework 4.7.2. This is also what's shown in the Visual Studio package manager.
Whereas on nuget.org, it has no entries whatsoever in the "Frameworks" section, but does list .NET Framework 4.7.2 in the "Dependencies" section.

If I add a reference to the package in a .NET Framework 4.7.2 project, then the "dotnet-outdated" tool is able to detect an available update,

For sure, this could eventually be argued to be an issue with the "dotnet-outdated" tool itself, as the now deprecated "NuKeeper" project is able to detect an update nonetheless.
But, it seems very strange to have only .NET Framework 4.7.2 listed in any case, so please look into this.