Migrate Table component away from material-table

[luciob]

The initial decision of using material-table component has to be dropped, in favour of standard Table component offered by @material-ui/core.

This action is required for the following reasons:

• wrong definition of peer dependencies causing issues on utilizing projects (for @material-ui/pickers, see pickers as a peer dependency mbrn/material-table#2259)
• hardcoded dependencies in package.json which reflect to multiple versions of same package in utilizing projects (for instance date-fns and the whole package of date-io/*, see https://github.com/mbrn/material-table/issues?q=is%3Aissue+is%3Aopen+date-fns+)
• our package shouldn't have dependencies unless strictly required, it now has 4 of which 1 is material-table and the other 3 are material-table peerDeps
• usages on utilizing projects does not justify the need for a custom lib, @material-ui/core does the job

We can consider to go back to it once it fixes the issues with packages and dependencies.

In the scope of this issue, also other Table related issues could be handled: #86, #87, #88, #98, #100, #101, #103

Of course current utilizing projects should have no or limited impact.
Test coverage to be as complete as possible.

[github-actions]

🎉 This issue has been resolved in version 2.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀