[TextareaAutosize] Sync height when the width of the textarea changes

[hbjORbj]

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

Closes #23641

Problem: as mentioned in the issue, change in the width of a textarea currently does not update the height. Hence, unwanted whitespace ends up existing in multi-line textarea.

Solution: use ResizeObserver API to observe the textarea and update the height in response to the textarea's resizing.

Consider the following textarea:

Without the implementation of this pull request (when there is change in the width of the textarea):

With the implementation of this pull request (when there is change in the width of the textarea):

[mui-pr-bot]

Details of bundle changes (experimental)

Generated by 🚫 dangerJS against b4a0777

[oliviertassinari]

1. I think that we can keep the window resize handler, for when ResizeObserver is not defined
2. I'm no longer sure we need a useResizeObserver abstraction. The usage of the native API seems simple enough. If we need to debounce, the story will be different.

[oliviertassinari]

No need to try catch nor to create a MockResizeObserve. We can test if ResizeObserver is defined and do nothing if it's not defined.

[hbjORbj]

This also prevents test failure, so I think we still need to include it?

[eps1lon]

This can't be merged at the moment. We need to wait for the next major version to communicate new browser support.

[oliviertassinari]

This can't be merged at the moment. We need to wait for the next major version to communicate new browser support.

@eps1lon

1. Could you expand on why we would need to wait for a new major?
2. What if we were making this a progressive enhancement? Meaning, that if the developer targets a subset of the browsers supported by ResizeObserver it works. If the developer supports a wider range of browsers, then we have 3 options, could either say a. broken as before. b. use a polyfill c. expose an action prop with an imperative API as we do for the <Tabs>. In each case, we could cover this as a "Limitation" in the docs, e.g. for IE 11.

[eps1lon]

Way simpler, looks great!

[eps1lon]

Could you expand on why we would need to wait for a new major?

The legacy bundle would've no longer worked in IE11.