(feat)O3-4671: Adding config to enable implementors add version number.

[suubi-joshua]

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

I have added a configuration to enable implementers add the version number of the distribution. This is beneficial for some implementers to debug when in the field.

Screenshots

Screencast from 02-06-25 11:24:07.webm

Related Issue

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

Other

[pirupius]

Not sure how the others feel but we could default this to false so that it doesn't affect other implementers.

[suubi-joshua]

True i thought I had set it to false, my bad.

[pirupius]

Let's change this to false since the default value for version is null

[jwnasambu]

@suubi-joshua Thank you so much for your work on this PR. Could you kindly fix the merge conflicts, please?

[pirupius]

Hi @denniskigen @ibacher do u have any thoughts on this addition.

The background is that we wanted a way to show the version number of the release to end users mostly for error reporting investing issues such as cache. This PR adds a simple optional config to indicate the version number as per this slack thread https://openmrs.slack.com/archives/CKS32D55G/p1745848235764369

[ibacher]

If we're going to support a version number, it should be a build-time constant, not set via config. Otherwise, I think the approach is fine.