[base-ui][Button] Maintain the disabled prop in SSR

[gitstart]

Description

Update button component to maintain button disabled prop across Next.js SSR

closes #38943

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

---

This code was written and reviewed by GitStart Community. Growing great engineers, one PR at a time.

[mui-bot]

Netlify deploy preview

https://deploy-preview-39212--material-ui.netlify.app/

Bundle size report

Details of bundle changes (Toolpad)
Details of bundle changes

Generated by 🚫 dangerJS against eade395

[simon-abbott]

I have not tested this, but one problem I ran into when making my local patch fix is hydration mismatching (i.e. the server adding the disabled prop, but the client-side code omitting it during hydration). I strongly suggest that these changes be tested thoroughly against the full matrix of options (button tag, a tag, and custom component, each with focusableWhenDisabled true and false) to make sure no such issues are being introduced.

[mj12albert]

nit on the title: I think the issue applies to all SSR, not just Next.js 😬

[gitstart]

Thanks for the feedback @simon-abbott, the implementation has been updated

[mj12albert]

I thought this would still cause some hydration mismatch errors (Next.js 😪 ) but I tested it a bunch and it seems to work ok!

CC @DiegoAndai for a quick review as well 🙏

[DiegoAndai]

thought this would still cause some hydration mismatch errors

I have the same thought: how is it not causing errors? 😅 For example, shouldn't this be an immediate hydration mismatch if passing a href prop so the tag would become 'A' client-side? Maybe I'm missing something.