[core] Prepare infra for pickers migration

[flaviendelangle]

Extracted from #3451
Part of #3608
Part of #2398

Codesandbox example to show that the babel config modifications don't break the grid.

• Sync .browserlist with the core

• Allow to use the core bundling strategy by re-importing scripts/build.js, scripts/buildTypes.js and copying scripts/copy-files.js (the current core file copy the license for each module, I will improve it later to only copy it if the package does not already have one)

• Add eslint rule to avoid import from a package inside itself

• Copy eslint rule from the core for the custom material-ui/mui-name-matches-component-name

• Rename yarn eslint into yarn lint to follow the code naming and enable the caching

• Edit the babel config to add @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object like in the core

[mui-bot]

These are the results for the performance tests:

Test case	Unit	Min	Max	Median	Mean	σ
Filter 100k rows	ms	1,109.7	1,721.4	1,278.7	1,393.48	263.746
Sort 100k rows	ms	665.3	1,211	1,211	976.42	208.975
Select 100k rows	ms	180.4	202.6	185	190.6	9.106
Deselect 100k rows	ms	98.6	146.5	143.9	123.7	18.759

Generated by 🚫 dangerJS against a335093

[github-actions]

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

[github-actions]

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

[m4theushw]

Why this change? I ran yarn lint in #3451 without it and test/utils/pickers-utils.tsx failed. Looking at this file, it seems that we could import CreateRendererOptions from @mui/monorepo/test/utils maybe.

[flaviendelangle]

I can't because there is no index.ts file at @mui/monorepo/test/utils so I can't import from there.
But I can add an eslint-disable-line to move on and propose a modification on the core

[github-actions]

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