(feat) O3-4277: Enable app-specific SWRConfig

[Twiineenock]

Requirements

• This PR has a title that briefly describes the work done including the ticket number. Ensure your PR title includes a conventional commit label (such as feat, fix, or chore, among others). See existing PR titles for inspiration.

For changes to apps

• My work conforms to the O3 Styleguide and design documentation.

If applicable

• My work includes tests or is validated by existing tests.
• I have updated the esm-framework mock to reflect any API changes I have made.

Summary

Description

Work in this PR allows app-specific SWR configurations for example the service queues and ward apps, ensuring their data refresh rates align with their real-time requirements.

Background

Both the service queues and ward apps are used to display near real-time dashboards for OPD/IPD workflows. A recent global configuration change in the SWR library increased the default data cache time to 30 minutes. While this change optimizes performance for many apps, it is not suitable for apps requiring more frequent updates.

Screenshots

Related Issue

https://openmrs.atlassian.net/browse/O3-4277

Other

[Twiineenock]

CC
@chibongho , @brandones, @denniskigen

[chibongho]

Thanks @Twiineenock . I think we should be able to have app-specific SWRConfig without changes to core. I'm thinking of just wrapping the root component in root.comonent.tsx (in the ward app and the service queues app) with <SWRConfig>.

[brandones]

I support this change. Doing it this way has two advantages:

1. We can merge custom SWR config options with our application default options
2. We avoid creating extra nested SWRConfig contexts

Maybe @ibacher or @denniskigen can weigh in, since @chibongho and I are at odds here?