BoxControl: Better minimum value support

[youknowriad]

Related #67625

What?

In some BoxControl components, (like for margin) we want to allow negative margins. This is done by passing min: -Infinity to the component. This is already partially supported and used but I've found that the "RangeControl" doesn't work in an optimal way: You can actually set any number in the Range control even if it's inferior to min

This is a tiny PR that just passes the minimum number down to the RangeControl when it's provided and different than an infinite value. It's not perfect but it's slightly better than what's in trunk.

Testing Instructions

• Run storybook locally npm run storybook:dev
• Define inputProps as something like { min: 10 } for the default BoxControl component story.
• Notice that the minimum is respected in both ways of changing the value.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: youknowriad <youknowriad@git.wordpress.org>
Co-authored-by: jorgefilipecosta <jorgefilipecosta@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[jorgefilipecosta]

LGTM to me, the change makes sense 👍

[github-actions]

Flaky tests detected in 2973557.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/12294380995
📝 Reported issues:

• [Flaky Test] should move focus to the block #38832 in /test/e2e/specs/widgets/customizing-widgets.spec.js