(feat) O3-3218: Make the schema validation(block/allow) render a configuration

[gitcliff]

Requirements

• [x] This PR has a title that briefly describes the work done including the ticket number. If there is a ticket, make sure your PR title includes a conventional commit label. See existing PR titles for inspiration.
• [ ] My work conforms to the OpenMRS 3.0 Styleguide and design documentation.
• [ ] My work includes tests or is validated by existing tests.

Summary

This PR is addressing the issue enabling on and off schema validation via configuration, also during schema validation the user should be shown the validation errors but still be able to render and saving their changes

Screenshots

https://www.loom.com/share/cfc15777ebcf4cc6991110cd06a08638

Related Issue

Other

[hadijahkyampeire]

Thanks @gitcliff but I think we should always show the validation errors and highlights, the config should only be attached to the render, whether to allow rendering with errors or not. And the default should be false, then implementations that want to enforce validation will turn it true.

[gitcliff]

Thanks @gitcliff but I think we should always show the validation errors and highlights, the config should only be attached to the render, whether to allow rendering with errors or not. And the default should be false, then implementations that want to enforce validation will turn it true.

@hadijahkyampeire the validation errors and highlights are show when the user clicks render their changes . Default is false

[hadijahkyampeire]

So @gitcliff the thing is that the errors showing shouldn't depend on the config, we want to show errors and their highlights even if the config is false, the only thing the config should allow/block is the rendering part.