Add notifcation when publishing varying culture without domains configured

[nikolajlauridsen]

This PR adds a notification in the UI as well as a log warning when a content editor creates a piece of multilingual content that has no domain configured for it, this fixes: #10350.

The pattern for what is considered a valid and what is not is a bit weird:

Assume a content type that varies in language A , B, and C the following rules apply as far as I can tell

• Root node - Published in language A
  • Child node - Published in language A

This is considered valid because only one language is published = we can route this

• Root node - Published in language A
  • Child node - Published in language A and B

This is invalid because there's more than one culture published in child node, so we can't route child node

• Root node - Published in language A, with domain for language A
  • Child node - Published in language A and B with, with domain for language B
    • Grandchild node - Published in language A and B

This is valid because somewhere in the ancestor path there's a domain for both languages A and B

• Root node - Published in language A, with domain for language A
  • Child node - Published in language A and B with, with domain for language B
    • Grandchild node - Published in language A, B, and C

This is not valid because there's no domain for language C anywhere

Testing

1. Add a couple of languages
2. Create a document type that varies by language
3. Start testing out some of the patterns above and ensure that the warning notifications show up when expected and that a warning is logged.

Please try some different combinations as well, there may have been some "rules" I've missed

[Zeegaan]

Found a few minor things (thank you stylecop)
Rest LGTM 👍

[Zeegaan]

With the changes (and the recent bugfix) i tested again and now everything works as it should 👍

Merging 💪