Feature: Use uui invalid color

[nielslyngsoe]

Fixes #17089
Fixes #18416

This PR. runs validation + server validation when saving Documents, without preventing save from happening.
Therefor this adjusts the validation feedback color for Saving vs. Publishing. So its not danger-red when Saving, just yellow.

[Welander1994]

The content node does get saved, but the feedback color is still danger-red and not yellow

[nielslyngsoe]

I just had to test it does work here, maybe installing latest npm dependencies was missing when Welander tested.

It does thought not inherit the yellow color scheme in the Block Workspace. But there validation issues are also preventing the user from submitting, so for now that is okay IMO. then we will correct that part of the experience later when we know if we like the user to be allowed to close modals with issues.

[madsrasmussen]

It is not related to this PR, but related to "the saving experience." 😄

I don't think it makes much sense to disable the save button until the user has entered something. We already allow saving an invalid document. Also, the "Save and Publish" button is enabled, which makes it even more confusing.

[madsrasmussen]

When saving a document, the saving process gets blocked by validation, which shouldn't be the case. I correctly see the "invalid" notifications. See the screenshot below. The save request doesn't get sent.

A small detail: I don't think the mandatory marker (*) should change color from red to yellow.

[nielslyngsoe]

@madsrasmussen I have corrected your suggestions. Though not the disabled save button, as it is not possible to save without a name.