fix: metabase

[jamil314]

Note

Currently, we do not run e2e tests as a check on opencrvs-countryconfig-repo PRs. Please ensure your PR doesn't break any e2e tests.

One method for doing this is to open a PR with these changes to opencrvs-farajaland as well, and see if the PR check passes there.

Description

Fixes (or finds to be already fixed) following tickets:

1. Some column values are not displayed in a human-readable format in Registry Dashboard. opencrvs-core#10778
2. ‘Birth Location’ field missing or shows location ID instead of readable name depending on 'type of birth location' selection. opencrvs-core#10758
3. ‘Registered on’ timestamp in Registry doesn’t match the ‘Registered’ action time on Record Audit page. opencrvs-core#10756
4. 'Location' filter options not appearing on Registry Dashboard. opencrvs-core#10769
5. 'Birth registration by district' widget shows birth registrations by District Registration offices instead of actual Districts. opencrvs-core#10784
6. Declarations created/ registered in any other place than Ibombo not showing up in Registrations Dashboard. opencrvs-core#10748
7. Health Institutions appear as options in Location filter, shows no result when selected. opencrvs-core#10793
8. 'Birth registration certification rate' showing 'No results' when filtered by location. opencrvs-core#10772

Checklist

• I have linked the correct Github issue under "Development"
• I have tested the changes locally, and written appropriate tests
• I have tested beyond the happy path (e.g. edge cases, failure paths)
• I have updated the changelog with this change (if applicable)
• I have updated the GitHub issue status accordingly

[github-actions]

Oops! Looks like you forgot to update the changelog. When updating CHANGELOG.md, please consider the following:

• Changelog is read by country implementors who might not always be familiar with all technical details of OpenCRVS. Keep language high-level, user friendly and avoid technical references to internals.
• Answer "What's new?", "Why was the change made?" and "Why should I care?" for each change.
• If it's a breaking change, include a migration guide answering "What do I need to do to upgrade?".

[cibelius]

Tested on my machine 👍