[docs] Add migration guide from alternative UI libraries

[oliviertassinari]

• I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡

Add documentation on how to migrate from alternative UI libraries.

Examples 🌈

• I have seen this idea implemented in Add migration guide from vanilla React vercel/next.js#17455, Add migration guide from Create React App vercel/next.js#17454, Add migration guide from Gatsby vercel/next.js#17453.
• It's also something we would see frequently in traditional products.

Motivation 🔦

As a user of another UI library, I have built my habit, trying another library requires a learning curve that I discouraging. We can't document everything but we can likely cover the most important differences. I can also help developers to compare objectively the different libraries, based on things they can directly see.

Libraries we could cover:

• AG Grid: map the main API differences, the customization paradigm shift
• Kendo UI: map the main API differences, the customization paradigm shift
• DevExpress React: map the main API differences, the customization paradigm shift
• react-table: Once we have the hook-only API, we could provide a find grain migration example, until then, we can probably focus on the high-level aspects.
• Ant Design table
• Material Table

⚠️ These guides won't be meant to marketing one solution over another, this would have to been done upstream in the pipeline. This step would be meant to reduce the friction in the transition.