fix(ui): allow negative values in validate-number-range (#40818)

[lbajsarowicz]

Description

ACP2E-3867 added a numeric pre-check /^(?:\d+\.?\d*|\.\d+)$/ to
validate-number-range. The regex rejects any leading minus sign, so UI
components declaring a range like validate-number-range -99-10000 reject
legitimate negative inputs even though the range explicitly allows them.

The dataAttrRange regex on the very next line already accepts -? on
both bounds, so the upstream short-circuit was the only blocker. Allow
an optional leading - in the numeric pre-check.

Updated the jasmine spec to reflect the correct expected behaviour for
negative ranges (the existing test was asserting the buggy result) and
added coverage for the mixed-sign range case from the issue.

Fixes #40818

Fixed Issues

• Fixes UI components validate-number-range validation rule no longer allowing negative values #40818: UI components validate-number-range validation rule no longer allowing negative values

Manual testing scenarios

Declare a UI component field with:

<item name="validate-number-range" xsi:type="string">-99-10000</item>

Before: any negative input fails with The value is not within the specified range.
After: negatives within the range pass; values outside the range still fail.

Contribution checklist

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All automated tests passed successfully (rules.test.js coverage extended)
• Changes to the codebase comply with technical guidelines

[m2-assistant]

Hi @lbajsarowicz. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

[lbajsarowicz]

@magento run all tests