Add Documentation Section on how to migrate to kapp-controller

[asaikali]

Users that are considering switching to kapp-controller from another solution need to invest a significant amount of effort to answer the following questions:

1. Is the migration possible for my usecase?
2. How do I perform the migration?
3. How do the concepts in the tool that I am currently using and familiar with map to concepts in kapp-controller?
4. Is kapp-controller at feature parity with the tool that I am currently using?

To answer questions around migration requires the users to become an expert at kapp-controller and the tool they are migrating from. Creating a documentation section called "Migrate to kapp-controller" that provides an easy to follow narrative that guides the user along what they need to learn & do to migrate can be very valuable and accelerate the adoption of kapp-controller.

[100mik]

Love the suggestion!
I imagine a lot of folks might be curious about how migrating from a popular tool like helm would look like.

This issue might belong in the carvel-dev/carvel repo as there might be other cases to consider as well. But some guidelines or blogs around the same would be helpful.
Leaving this in the triage state as this issue might be moved around and broken down to more specific use cases.

[github-actions]

This issue is being marked as stale due to a long period of inactivity and will be closed in 5 days if there is no response.