Aggregate errors in package parsing

[hasheddan]

What problem are you facing?

Currently, the package parser will return with error as soon as it encounters an issue. This means that a user building a package with multiple errors will have to fix each issue one by one and rebuild to see if the package is well-formed between each step.

How could Crossplane help solve your problem?

The package parser should identify all errors and aggregate them so that users both building and installing packages can have a comprehensive view of all errors that must be corrected.

[negz]

@hasheddan Any thoughts on how we'd present an aggregated array of errors cleanly? iirc there's a couple of different places in which we'd return these - e.g. kubectl crossplane, revision events, etc?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.