(feat) O3-1494: Add report admin dashboard

[pwargulak]

Summary

The PR contains implementation of Report administration pages, including:

1. Reports overview page which shows history of Report executions, inc current and planned execution.
2. Reports schedule where user can schedule reports to be execute once at some time later, daily, weekly at specific day(-s), monthly at the end or start of a month (this is a copy o OMRS 1.x functionality).

Pages are accessible via System Administration menu.
It implements designs documented here (newest mocks section).

Screenshots

Issue

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

[gracepotma]

I expect that Palladium-Kenya will be interested in using this so I reached out to @ojwanganto: @jecihjoy he recommended you review this PR :)

[pwargulak]

Changed to DRAFT, because it's not adapted to changes in API in openmrs/openmrs-module-reportingrest#33

[gracepotma]

So TBH I didn't notice until now that this PR is almost 12k lines of code - woah. Reviewing this make take our support & community members quite some time. In future smaller PRs earlier would be more advisable :) Hope that makes sense!

[ojwanganto]

@gracepotma - Should we have this work as part of the admin tools or a separate reporting-esm?

[ibacher]

@ojwanganto Well, it is a separate esm, just in this mono-repo. I don't think we need individual GitHub repos for everything.

[ojwanganto]

Makes sense @ibacher. I think i didn't get into the source code. I just looked at the project URL. Sorry about that

[ojwanganto]

@pwargulak when do you think we can start testing this work? It already provides a good foundation for the reporting functionality we need

[pwargulak]

@ojwanganto We are working on bringing the BE code to sufficient quality, the PRs related to BE are listed here once they are merged we'll adapt the FE (this PR) and then it can be tested.

[ojwanganto]

Thanks for the update @pwargulak.

[tendomart]

Iam curios to know if anyone has used this.. may need it somewhere @pwargulak @jecihjoy

[druchniewicz]

@denniskigen @ibacher as two required backend PRs have been merged I adapted this PR to mentioned backend changes and open PR once again for review. Can you take a look? Piotr's first comment gives a quick overview what has been done here

[druchniewicz]

@ibacher @denniskigen @jecihjoy I kindly remind you about this PR. Can you take a look?

[ojwanganto]

Looping in @makombe @donaldkibet

[druchniewicz]

@denniskigen @ibacher @brandones @jecihjoy @makombe @donaldkibet
can you take a look at pull request? I would like to make this PR mergable to allow people using it

[denniskigen]

Thanks for getting this off the ground, @pwargulak! I've left some suggestions.

[druchniewicz]

@denniskigen I addressed your comments and also make similar corrections in other places in app, not only with those indicated by you. Can you take a look?

[druchniewicz]

Hey @denniskigen , will you be able to look on my latest changes? (made according to your last comments)

[druchniewicz]

@denniskigen

[druchniewicz]

Hi @denniskigen , next changes have been pushed. Can you take a look?

[denniskigen]

Great work getting this over the line, @druchniewicz @pwargulak! Here's some additional changes to consider as potential future iterations:

1. Migrating from the custom overlay implementation in favor of using the Workspace system. Read more about the Workspace API here.
2. Add empty states to the widgets in the UI for when there is no data to show to the user.
3. Migrate form logic to React Hook Form and Zod for reduced boilerplate, type-safe validation and improved performance.
4. Migrate from using breadcrumbs as a navigational pattern. @ciaranduffy @paulsonder, could you advise on what the ideal navigational pattern for pages like these should be?

[denniskigen]

Thanks for the great work! Merging shortly; the e2e test failure seems unrelated to your changes.

[druchniewicz]

Thanks for the great work! Merging shortly; the e2e test failure seems unrelated to your changes.

Thanks @denniskigen for reliable code review and suggestions how your comments should be addressed!

[denniskigen]

Another important next step I forgot to mention: adding the reports app to the reference application's spa-assemble-config.json file so it gets included in the importmap.