discuss potential improvements for MCP error reporting

[Diaphteiros]

What this is about

During today's dev sync, we shortly discussed the topic of MCP error reporting and decided that there was room for improvement, mainly in these points:

1. We would like to be able to distinguish errors that are based on a wrong end-user configuration (e.g. invalid crossplane provider version selected) from other errors. This would not only enable us to provide faster and more precise feedback to customers by directly telling them that their configuration is wrong, it would also help the DoD to ignore these errors, as this cannot be solved by the DoD.
2. For customers, it is not immediately clear whether a Not Healthy on an MCP means 'this MCP is completely unusable' or 'everything except for one service works fine'. We want to improve this by better distinguishing between different errors.

For both points, we have not yet a clear vision on how exactly we want to achieve them.
The goal of this task is to have a discussion about this topic which should result in new tasks that specify exactly how to implement the desired features.