NuGetAudit in VisualStudio with packages.config projects does not support configuring audit properties for projects sharing the same name

[nkolev92]

PackageRestoreData should use the project path instead of the project name when restoring

• PackageRestoreData is the type that's used to represent a package from any packages.config in a single restore operation.
  It contains the deduplicated id and the list of projects names that are relevant to it.

https://github.com/NuGet/NuGet.Client/blob/dev/src/NuGet.Core/NuGet.PackageManagement/IDE/PackageRestoreData.cs#L11-L13

• On the CLI, these PackageRestoreData name is the project file.
• In VS, this tends to be the project name.

In AuditChecker, the PackageRestoreData key is compared to the AuditInfo key:

https://github.com/NuGet/NuGet.Client/blob/2d9dbdb4140df7bccbb1df768c64617b661239ff/src/NuGet.Core/NuGet.PackageManagement/Audit/AuditChecker.cs#L224.

The problem, project path is unique, while project name isn't required to be.

What this means is that long term, we need to switch from using the name, to using the project path.
The challenge is that the PackageRestoreData has a lot of usages.

In order to fix #13465, we had to make an assumption in there with a known limitation, basically meaning that projects with the same name will have the same audit configuration.

The chances of anyone configuring msbuild audit properties differently within the same solution are low, but still a possibility nonetheless.