Paket uses package name from dependencies file instead the one from NuGet for HintPath

Description

Latest paket version (not sure when it changed though) changes all casings in the HintPath property of System.Text.Json to .JSON - This causes a "dirty" solution for our devs every time they run a paket install for unrelated upgrades. It makes diffing hard and people are unsure if they should commit the change or not. Also not all devs are using the same paket version at the same moment, so its flipping between both states. They are also hesitant since they expect it could change back to lower casing at some point.

The initial mistake was though to have the package name spelled incorrectly in dependencies file - it was JSON there. When we fixed that things went back to normal.

Repro steps

• Reference System.Text.JSON (wrong casing) package in any dependencies file

Expected behavior

• .csproj files continue using System.Text.Json for the HintPath property

Actual behavior

• .csproj files are changed to System.Text.JSON

Reproduce the issue with a dependencies file referencing System.Text.JSON and inspect how Paket generates the HintPath in the affected .csproj files. Trace where the package name from the dependencies file is used instead of the NuGet name. Done means HintPath uses System.Text.Json consistently despite incorrect casing in the dependencies file, with regression coverage if the project’s tests provide a suitable entry point.