Server-Side Component Config Validation

[fa9r]

Describe changes

When creating or updating stack components through the dashboard, we now also validate that the component config matches the corresponding configuration class and that the component is configured correctly.

Pre-requisites

Please ensure you have done the following:

• I have read the CONTRIBUTING.md document.
• If my change requires a change to docs, I have updated the documentation accordingly.
• If I have added an integration, I have updated the integrations table and the corresponding website section.
• I have added tests to cover my changes.
• I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Other (add details above)

[strickvl]

Can we add a test(s) for the updated client functionality? Otherwise looks good to me.

[fa9r]

@strickvl I didn't add any Client functionality. Did you mean the util functions?

[strickvl]

You added the validation

[fa9r]

You added the validation

That was already part of the client before, all I did is refactor it out into a util function that is now called by the endpoints as well

[strickvl]

LG from my side, pending a green test suite.