Report argument modal translation

[fergie-nz]

Fixes #4951

👩🏻‍💻 What does this PR do?

Adds translations to report modal via json schema or UI schema.

Utilised inbuilt JSON form translation.

Maintains type safety of locale keys!

💌 Any notes for the reviewer?

🧪 Testing

You can test by running the 'Report-argument-modal-translation-example' branch which includes an example translation in the itemUsage report for both methods of adding translations

• Go to reports
• Open item usage report
• See translation

Note - you may need to clear out existing reports in your database to view.
Delete reports, then run your back end. This will populate with updated report automatically

📃 Documentation

• Part of an epic: But also documentation added in PR

[fergie-nz]

Also made a PR to update reports repo docs:

https://github.com/msupply-foundation/open-msupply-reports/pull/118

[fergie-nz]

memoized keys in case checking Object.keys repeatedly is expensive. Unsure if it would be for how many keys we have.

[andreievg]

Looks great, does it work for our patient schema too:

open-msupply/server/service/src/programs/schemas/patient.json

Line 113 in 512275c

"FEMALE",

Can you do an example of how it works for enums in that default patient schema ?

Also do you have a list of tasks to finish this issue fully ?

[fergie-nz]

Looks great, does it work for our patient schema too:

open-msupply/server/service/src/programs/schemas/patient.json

Line 113 in 512275c

"FEMALE",

Can you do an example of how it works for enums in that default patient schema ?

Also do you have a list of tasks to finish this issue fully ?

I hadn't considered the patient schema!

I'll have a look.

I do not have a list of tasks to finish this issue fully

[fergie-nz]

Can you do an example of how it works for enums in that default patient schema ?

Yes with a small modification of how we add enums in our schema.

I will create an example of this and update the docs

[github-actions]

Bundle size difference

Comparing this PR to main

Old size	New size	Diff
4.97 MB	5.06 MB	92.06 KB (1.81%)

[fergie-nz]

Can you do an example of how it works for enums in that default patient schema ?

Also do you have a list of tasks to finish this issue fully ?

I've had a look and this requires a few more changes.

It is a little over my head so will take a bit of time to figure out.
I've paused now because not obvious to me. Do you think worth looking into?

There are a couple of factors:

• Our custom renderers don't accept the inbuilt JsonForms translation functionality
• We stringify our patient schema in rust. If we are passing into rust, might as well translate there now rather than converting then re translating on the front end? If I am understanding how we manage the patient schema correctly