[BUG] VCC allows installing packages requires Unity 2021.3 to Unity 2019 projects

[anatawa12]

Describe the bug

VCC allows installing packages requires Unity 2021.3 to Unity 2019 projects.

Since VPM is convenient package distribution, some Generic Unity tools are also distributed as VPM package.
For such a packages, specifying unity field to 2021.3 is very reasonable since Unity 2021.3 is (legacy) LTS

To Reproduce

1. Create Unity 2019 Project
2. Add Anatawa12's Test VPM Repository for VCC's bug to your VCC
3. Add Package Requires Unity 2021.3 to the project
4. VCC allows installing Package Requires Unity 2021.3 to the project without any warning.

Expected behavior

VCC should

• Warn Package Requires Unity 2021.3 is not compatible with 2019 and ask migrate to 2022
• Warn Package Requires Unity 2021.3 is not compatible with 2019 and refuse installing the package

Screenshots

No response

Related Product

VCC (VRChat Creator Companion)

Product Version

2.2.2

OS

Windows 11

Additional context

Related issues

• [BUG] Incorrect interpretation of unity field of package manifest and impossible to declare package compatible with both 2019 and 2022. #367
• [FEATURE] Check for Unity version before installing some package #311

There already is one real-world example of packages requires unity 2021.3.
That is TexTransTool v0.5.0-beta by Reina Sakiria.
In addition, my AvatarOptimizer is planned to require unity 2021.3 if it's still LTS when I drop Unity 2019.

[orels1]

Available in VCC 2.2.4