Package name validation throws errors into the Console instead of Inspector when editing the dependencies of a custom package

How to reproduce:
1. Create a new Unity project
2. Open the Package Manager (Window -> Package Management -> Package Manager)
3. Click the "+" button -> Create package 
4. Go to Manage -> Edit Manifest
5. In the Inspector, go to the "Dependencies" and add a new item
6. Enter a random package name or create the two dependencies of the same name
7. Observe the Inspector

Expected results: Validation errors are thrown into the Inspector
Actual results: Validation errors are thrown into the Console only when clicked "Apply"

Reproducible with: 6000.3.0a4
Can't test with: 6000.0.55f1, 6000.1.15f1, 6000.2.0f1 (no such functionality)

Reproducible on: Windows 11 Pro
Not reproducible on: No other environment tested