feat: refactor & make indigo patches more readable

[Faraz32123]

• refactor, simplify & make indigo patches more readable
• separate react components from patches folder and render them cleanly, this also improve development of react components in jsx files instead of patches.
• close Refactor & simplify tutor-indigo patches and move react components out of patches #201

[ahmed-arb]

Thanks @Faraz32123, this is a much-needed upgrade 👍

One question though: do we really need the mfe-env-config-buildtime-imports patch component? At the moment, I don’t see a strong case for having multiple import patches. If we’re only going to maintain a single import, it might be simpler and more maintainable to keep the imports directly inside the patch itself rather than abstracting them into a separate component.

[Faraz32123]

Thanks @Faraz32123, this is a much-needed upgrade 👍

👍 Thanks,

One question though: do we really need the mfe-env-config-buildtime-imports patch component? At the moment, I don’t see a strong case for having multiple import patches. If we’re only going to maintain a single import, it might be simpler and more maintainable to keep the imports directly inside the patch itself rather than abstracting them into a separate component.

I understand your concern. But it's more about readability and keeping the react components & their imports in same directory without any warnings & formatting errors.
If we see Example.jsx file. It says, add your imports to Imports.jsx which doesn't give import warning like mfe-env-config-buildtime-imports patch. And we can't remove mfe-env-config-buildtime-imports patch due to backward compatibilty i.e. if some people are using this patch.