Enhance server side validation of existing aggregates

[HaniAlshikh]

Currently two tenants with the same name but different case could be created. This must not be possible! For all other aggregates the name must be case insensitive unique!

[jastBytes]

LGTM but as we are on this anyhow we should make sure that all strings are trimmed when aggregates are created/updated. Your change handles that things are compared trimmed, but they would still be stored with whitespace. Could you look into that too please?

[HaniAlshikh]

Oh yeah, I really feel ashamed for missing this point. I think I was too concentrated on the slices.contains requirement that I didn't give the rest enough thought. You are totally right will do this now.

[coveralls]

Coverage decreased (-0.06%) to 59.097% when pulling e00adcf on enhancement/enhance-server-side-validation-of-existing-aggregates into 9259187 on main.

[HaniAlshikh]

We discussed this again and decided that it's not the Server's job to do any cleanup or data modification, as this will implay side-effects the client might not have accounted for therefore we will make the command data validation more strict and expect the client to handle any cleanup if necessary