[charts] Stabilize useSeries and useXxxSeries hooks

[JCQuintas]

Also added docs to all public hooks

Changelog

• The useSeries and useXxxSeries have been stabilized and renamed accordingly. Removing the unstable_ prefix. — Learn more.

[mui-bot]

Deploy preview: https://deploy-preview-15545--material-ui-x.netlify.app/

Updated pages:

• docs/data/migration/migration-charts-v7/migration-charts-v7.md

Generated by 🚫 dangerJS against 6d2192a

[codspeed-hq]

CodSpeed Performance Report

Merging #15545 will degrade performances by 10.6%

_{Comparing JCQuintas:remove-unstable-useseries (6d2192a) with master (7914aa5)}

Summary

⚡ 1 improvements
❌ 1 regressions
✅ 4 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	master	JCQuintas:remove-unstable-useseries	Change
❌	BarChartPro with big data amount	325.5 ms	364.1 ms	-10.6%
⚡	ScatterChartPro with big data amount	193.8 ms	174.9 ms	+10.83%

[alexfauquette]

I'm wondering if the current hook is the best DX. If we provide something like

useBarSeries(['seriesId1', 'seriesId2']) // Returns the config of the series
useBarSeries() // Returns all bar series in the correct order

It might be easier to use

[JCQuintas]

Do you see a lot of value in returning an array for allowing multiple items to be returned or only allow one return per call?

const a = useSeries('a')
const b = useSeries('b')

vs

const [a,b] useSeries('a', 'b')

[alexfauquette]

The array has the advantage to be easier to understand and to allow adding extra arguments later. But I'm not sure if passing an array like useBarSeries(['seriesId1', 'seriesId2']) could cause perf issue because at each render it would creat a new array 🤔

Maybe we should wait for the end of the plugin migration to see if one DX allows easier perf otpimisation than the other

[JCQuintas]

The array has the advantage to be easier to understand and to allow adding extra arguments later. But I'm not sure if passing an array like useBarSeries(['seriesId1', 'seriesId2']) could cause perf issue because at each render it would creat a new array 🤔

Maybe we should wait for the end of the plugin migration to see if one DX allows easier perf otpimisation than the other

Optimisation-wise we can just ...args into the dep array. Though we have to disable the eslint error for exaustive deps 🙃

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.