Editing Package Manifest allows adding a Dependency with a null version

Steps to reproduce:

1. Package Manager window > + > Create package
2. Click Manage -> Edit Manifest
3. In the Inspector window, add a new Dependency
4. Set the Dependency name to test2
5. Leave the version section empty
6. Click the Apply button

Actual results: There is no data validation for the Dependency Version fields, allowing for package compilation-breaking changes to be applied

Expected results: The Dependency Version field has data validation to safeguard against a null package version

Reproducible with versions: 6000.3.0a4

Can’t test with versions: 6000.3.0a2 or earlier (Feature was introduced in 6000.3.0a3)

Tested on (OS): macOS 15.5, Ubuntu 24

Notes:

• While the error is thrown after applying the changes, if it is missed initially, it's hard to figure out which package is causing the issue. The error states which dependency lacks a version, but does not state which package is affected.
• There are no visual indicators of which package is broken either. If the user reselects the package, the broken dependency will not show up in the Dependency List
• Edit mode does have data validation for Dependency name fields, but its missing for the version fields