chore: upgrade BoundsControl to TS

[ad-m]

SUMMARY

Upgraded BoundsControl to TypeScript to apply direction outlined in #18100 .

Added storybook for BoundsControl.

In long term I will consider change emitted by onChange value to (number | undefined) to keep consistent with (number | undefined) of InputNumber.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

No visual changes.

Values might be provided in the appropriate input form.

ADDITIONAL INFORMATION

• Has associated issue: see Migrate components to TypeScript #18100
• Required feature flags: no
• Changes UI: no
• Includes DB Migration (follow approval process in SIP-59): no
  • Migration is atomic, supports rollback & is backwards-compatible: N/A
  • Confirm DB migration upgrade and downgrade tested: N/A
  • Runtime estimates and downtime expectations provided: N/A
• Introduces new feature or API: no
• Removes existing feature or API: no

@kgabryje , @mik-laj You might be interested in this PR!

[geido]

Hey @ad-m just a hint, you don't need to check all the boxes under "Additional information" in your PR description. Just check those that apply :)

[geido]

One suggestion for you, I'd say that smaller contributions are good but in order to keep things together and avoid fragmentation, we could group more work under one PR. For instance, what do you think about converting this component to a functional one? This PR seems the perfect place to do that!

Also, thank you very much for adding stories to Storybook. That's gold!

[ad-m]

One suggestion for you, I'd say that smaller contributions are good but in order to keep things together and avoid fragmentation, we could group more work under one PR. For instance, what do you think about converting this component to a functional one? This PR seems the perfect place to do that!

I will convert it to FC. I can do it in this PR, and I can do it separately - as you prefer. I am open to doing whatever it takes to ensure that the review works efficiently and the work of the commiters is minimized.

I can see that this is not a technically attractive issue (but long-term important for the condition of the project, so perfect for someone who is just getting to know the structure of the project, like me), so it's harder to get a voluntary review, so I'm afraid that PR's like that will not get stuck. For reasons external to the project (personal), such a state of the matter would be uncomfortable for me, and small steps are always something forward.

[codecov]

Codecov Report

Merging #18200 (32a7872) into master (4e2bdd4) will decrease coverage by 0.00%.
The diff coverage is 88.88%.

@@            Coverage Diff             @@
##           master   #18200      +/-   ##
==========================================
- Coverage   66.30%   66.30%   -0.01%     
==========================================
  Files        1595     1595              
  Lines       62632    62628       -4     
  Branches     6309     6308       -1     
==========================================
- Hits        41529    41526       -3     
- Misses      19453    19454       +1     
+ Partials     1650     1648       -2     

Flag	Coverage Δ
javascript	51.37% <88.88%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
.../src/explore/components/controls/BoundsControl.tsx	88.88% <88.88%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4e2bdd4...32a7872. Read the comment docs.

[geido]

/testenv up

[github-actions]

@geido Ephemeral environment spinning up at http://34.219.155.104:8080. Credentials are admin/admin. Please allow several minutes for bootstrapping and startup.

[geido]

LGTM with a nit

[github-actions]

Ephemeral environment shutdown and build artifacts deleted.