WIP - Fix Nested Validation

[djabarovgeorge]

What change does this PR introduce?

The PR introduces WIP of what we need to do in order to fix the nested validation that currently is broken. In order to add nested validation to the variants we will need to do the following:

• Create a custom validation decorator.
• Fix the nested validation that does not work at the moment. In order to fix it we need to do the following add ValidateNested decorator, if it is an array we should add each as well (@ValidateNested({ each: true })), then add @Type(() => NotificationStepVariant) decorator from class-transformer in order to map the type implicitly.
• The hardest part IMO will be to return the nested errors that we will get, at the moment we throw an exception on the first layer, but it an error is not thrown we do flat on the first layer on BaseComman which won't return us the nested constrains.

Why was this change needed?

So we could validate nested objects and return a valid error if validations had errors.

Other information

In this PR I am adding nested validation only for variants as POC, once we merge this PR we most definitely need to validate all of the rest ValidateNested decorators.

DOD

• Add unit tests for the extractConstraints function.
• Add tests of command in order to check that the new logic works with it as expected.
• Add max validation depth in order to not over-compute extractConstraints if the input is unexpectedly long or infinite.

[ainouzgali]

@djabarovgeorge thanks for doing this!! Left a couple of comments

[ainouzgali]

Suggested change

	@IsBoolean()
	@IsString()

[ainouzgali]

I believe this should be added in update-notification-template.command as well

[github-actions]

This PR is being closed due to inactivity. Please reopen if work is intended to be continued.