Add Value Coercion to ConstrainedBox

[michael-hawker]

Fixes #4166 too

Adds Value Coercion to the properties to ensure they're within a valid range.

Also fixes the issue with MultipleX/Y not triggering layout updates.

Debating whether to add more tests to this PR or not still... 🤔

PR Type

What kind of change does this PR introduce?

• Bugfix

What is the current behavior?

Can specify any values for properties.

What is the new behavior?

Will reset/bound properties to expected values if out-of-range.

PR Checklist

Please check if your PR fulfills the following requirements:

• Tested code with current supported SDKs
• Pull Request has been submitted to the documentation repository instructions. Link:
• Sample in sample app has been added / updated (for bug fixes / features)
  • Icon has been created (if new sample) following the Thumbnail Style Guide and templates
• New major technical changes in the toolkit have or will be added to the Wiki e.g. build changes, source generators, testing infrastructure, sample creation changes, etc...
• Tests for the changes have been added (for bug fixes / features) (if applicable)
• Header has been added to all new source files (run build/UpdateHeaders.bat)
• Contains NO breaking changes

Other information

[ghost]

Thanks michael-hawker for opening a Pull Request! The reviewers will test the PR and highlight if there is any conflict or changes required. If the PR is approved we will proceed to merge the pull request 🙌

[michael-hawker]

Alright added all the tests, should be descent coverage for now until we get real-world scenarios of usage. This PR ready to review.

[ghost]

This PR has been marked as "needs attention 👋" and awaiting a response from the team.

[michael-hawker]

@chingucoding know you had called out the Value Coercion initially, so let me know if you want to review or not?

[marcelwgn]

Sure @michael-hawker , I would love to review this in the next few days!