Feature sets can install old version of packages even though not a dependency of any other package

Steps to reproduce:

1. Open a new Unity Project
2. Open Package Manager via Window > Package Manager
3. Navigate to the Unity Registry section
4. Click on the 3D Characters and Animation Feature Set (includes 4 packages)
5. Note that if you click on Cinemachine under Packages Included, it says it will install Cinemachine 3.1.1
6. Click Install for the Feature Set and wait for the install to complete
7. Observe the installed Cinemachine version

Actual results: Cinemachine 2.10.1 is installed. The Feature Set will say that this is because at least one other package or feature depends on it, however if you check the Cinemachine package, nothing else is using it but the Feature Set itself. 

 

Expected results: Cinemachine 3.1.1 is installed

Reproducible with versions: 6000.0.15f1

Not reproducible with versions: 2022.3.40f1, 2021.3.40f1

Can't test with versions: 

Tested on (OS): Windows 10/11

Notes:

• A particular pain pain point is that users can be missing out on up-to-date features added in the recommended version of the package for the particular Unity version. The package being locked by the Package Manager discourages users from manually updating.
• Outdated package versions installed via feature sets: 
  • 2D feature set installs 2D Animation 10.1.2 instead of 10.1.3
  • 3D Characters and Animation feature set installs Cinemachine 2.10.1 instead of 3.1.1
  • 3D World Building feature set installs Terrain Tools 5.1.0 instead of 5.1.2
  • Cinematic Studio feature set installs Cinemachine 2.10.1 instead of 3.1.1
  • Gameplay and Storytelling feature set installs Cinemachine 2.10.1 instead of 3.1.1