[Slider] Prevent rendering for marks that are out of min&max bounds

[abriginets]

This fixes an issue when Slider component renders marks that are out of min and max bounds, e.g. when user wants to render a mark for 120 value when min is 0 and max is 100. See CodeSandbox for reference.

P.S. - sorry for posting this PR twice. I accidentally checked out into outdated version of mui.

• I have followed (at least) the PR section of the contributing guide.

[mui-bot]

Details of bundle changes

Generated by 🚫 dangerJS against 3f4ba1e

[mnajdova]

The changes makes sense to me 👍 It's easier to review by hiding whitespace - https://github.com/mui/material-ui/pull/32436/files?diff=split&w=1

Considering the base Slider is used in the Mateiral UI slider (which is unfortunate at this moment), I would say this is a breaking change, but I am willing to push this, as I would say is a bug fix, rather than change in behavior. cc @michaldudak what are your thoughts on this?

---

I remember that there was an issue for this, could you please share it in the PR description?

[michaldudak]

I agree - rendering marks outside of the slider range doesn't look like a feature someone would depend on.

Side note:
This, however, gave me an idea of another feature we could implement one day - decouple rendered min and max from values available to select - so a slider could always be rendered from, say, 0 to 100, but values available to select could be restricted to 10-90. It could be handy where min and max are set dynamically in relation to another value and we want to show that in certain conditions selection of values outside of the currently available range is possible.

[mnajdova]

Looks great, I believe we can merge this. Thanks @abriginets