Update Package Validator for Unified Dependencies

[LittleCoinCoin]

Acceptance Criteria:

• package_validator.py updated to validate unified dependencies object structure
• System dependency validation implemented (package manager compatibility, platform checks) --> For now, it doesn't really make sense that we would be responsible for that. This will be handled by the package manager itself when the user tries to install. Of course, this will be subject to user validation, at least. But that's on the side of Hatch, not Hatch-Validator.
• Docker dependency validation added (image format, registry accessibility) --> Same as for system dependencies, it doesn't really make sense that we would be responsible for that. This will be handled by docker itself when the user tries to install. Before that, only the main dockerhub registry of images is allowed.
• Security validation hooks integrated at dependency level See Add Security Scanning Integration #10
• Support for both v1.1.0 and v1.2.0 schemas with automatic detection
  • Same as for the registry, given that there are no packages deployed yet, 1.2.0 could become the default.
  • That being the case, preparing an infrastructure that can easily receive new validator for future versions of the package json schema makes sense. Do we want to do it now?
• Clear, actionable error messages for each dependency type validation failure
• Test coverage for all new dependency fields

Dependencies:

• Requires Hatch-Schemas Issue Create Package Schema v1.2.0 with Unified Dependency fields Hatch-Schemas#8

[LittleCoinCoin]

Objectives covered by #12