Provide more informative errors in package parser

[hasheddan]

What problem are you facing?

Currently the package parser will return generic, "object-level" errors, such as not recognizing an object when there is an issue with the schema. It also has no concept of files, which can make it difficult to find where the error resides when building a large package.

How could Crossplane help solve your problem?

The parser should provider more informative errors, which will likely require passing down logic from the parser backends to provide additional context (e.g. file path from the FsBackend).

[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.