[system][zero] Move zero runtime related packages

[brijeshb42]

from the separate repo

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

[mui-bot]

Netlify deploy preview

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

Bundle size report

No bundle size changes (Toolpad)
No bundle size changes

Generated by 🚫 dangerJS against fc7fc61

[Janpot]

@brijeshb42 I don't have the bandwidth to go through all the code. I'll try to go through it diagonally. I assume the business logic has been reviewed on its original repo? Did you have to change much compared to your original setup? Anything you had to hack around or noticed any rough edges?

[brijeshb42]

@Janpot Yes. Main logic has already been reviewed. The change specifically for the zero runtime packages is that it still uses the same build step (as in the separate repo) which uses tsup and does not use standalone build folder with package.json.
I am also investigating why this is failing.

[Janpot]

The change specifically for the zero runtime packages is that it still uses the same build step (as in the separate repo) which uses tsup

Will we keep it that way or migrate?

[brijeshb42]

The plan is to keep it that way in the short term to focus on the actual development and migrate away in the long term.

[brijeshb42]

@mnajdova This PR is now ready for review after all the build related problems are solved.

[mnajdova]

From the initial testing, everything seems to work 🎉 I left two thins to be checked before merging.

After the merge, we need to cleanup the example app and provide structure for how we are going to validate that the migrated components work.