feat: focusout trigger + changeOrX behavior change

[Sayan751]

BREAKING CHANGE: This commit changes the default behavior for the changeOrBlur trigger.

• The change trigger is ineffective till the associated property is validated once, either by manual validation or by blur-triggered validation. This prevents showing validation failure immediately in case of an incomplete input. Note the distinction made between incomplete and invalid input.
• The blur trigger is ineffective until the property is dirty; i.e. any changes were made to the property. This prevents showing a failure message when there is a blur event w/o changing the property. This closes #509.

Additionally, this commit also adds 2 new validateTriggers namely focusout, and changeOrFocusout and respective binding behaviors. As it is quite evident from the name the triggers are based on focusout DOM event. The difference between blur and focusout is that the later bubbles. It is useful for custom elements, containing input elements. The changeOrFocusout is similar in nature of changeOrBlur, as described above. This closes #543.

[Sayan751]

@bigopon check this repo to play with the changes https://github.com/Sayan751/new-validation-ux-demo-pr-544

[bigopon]

@EisenbergEffect @Sayan751 Maybe there's some details that I miss but this looks good to me. Maybe you need to reverse the dist file as they are processed as part of the release @Sayan751

[bigopon]

I'm not sure why the CI failed but my local builds just fine 🤔

[Sayan751]

@bigopon @EisenbergEffect reverted the dist.

The CI is failing probably due to the type definition generated + old TS version. The build is also failing in master.

[bigopon]

@Sayan751 nice work! lgtm 🎉

[EisenbergEffect]

@Sayan751 Anything else needed or is this ready for merge?

[Sayan751]

@EisenbergEffect I have nothing else to push in this PR. This is ready for merge.

[bigopon]

Thanks @Sayan751 awesome work. You've got magic hands with our plugins 😁

[Sayan751]

@bigopon Very kind words 😊 Wouldn't have been same without the help from everyone involved though, including code review, community discussions etc. Oh boy! That sounds like a speech after winning academy awards. 😛

I want to see this getting used by devs, to understand if this new behavior suits most of them. Reason being that this is a delicate but breaking change.