Next 16 cache components `next-intl` incompatibility

[notilmi]

As we all knew Next.js 16 introduced cache components which revamped whole nextjs data fetching causing problems to our beloved next-intl package that we highly dependant of. Though this issue is already solved in the next-intl mainstream, due to our app pre-existing configuration making this issue harder to fix.

Any update on this will be updated in this issue.