Resolve validation error

[Horiodino]

This PR enhances the limayaml.Validate() function to collect and return all validation errors found in a Lima template, instead of stopping at the first encountered error.

Fixes: #3606

Updated the validation logic to accumulate multiple validation errors.

[Copilot]

Pull Request Overview

This PR updates the validation logic to accumulate all errors found in a Lima YAML template and return them together, rather than bailing out at the first error. Tests are adjusted to verify substrings in the combined error message.

• Replace single-error returns with errors.Join accumulation in Validate, validateFileObject, and part of validateNetwork
• Wrap the aggregated errors at the end of Validate with a "validation failed: %w" prefix
• Update unit tests to use assert.ErrorContains when expecting error messages

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
pkg/limayaml/validate.go	Switched early return calls to error accumulation; added final wrapping of all errors
pkg/limayaml/validate_test.go	Changed assertions from assert.Error to assert.ErrorContains

Comments suppressed due to low confidence (1)

pkg/limayaml/validate_test.go:19

• Add a new test where multiple invalid fields are set simultaneously, and assert that Validate returns all errors to ensure aggregation behaves as expected.

func TestValidateProbes(t *testing.T) {

[alexandear]

please revert:

Suggested change

	assert.ErrorContains(t, err, "field `additionalDisks[0].name is invalid`: identifier must not be empty")
	assert.Error(t, err, "field `additionalDisks[0].name is invalid`: identifier must not be empty")

[jandubois]

Thanks, LGTM