feat: add filter period to iframe src for custom widgets

[EdsonNhancale]

Key features

1. Support for adding pe (period) as a query parameter in the iframe source URL.
2. Dynamically appends the pe parameter to the iframe source when the filter is applied.

---

Description

This update ensures that the pe (period) filter is included in the iframe URL for dashboard items when the filter is applied. If the pe filter is present in itemFilters, the periods are concatenated using , as the delimiter and added as a period query parameter in the iframe source.

---

TODO

• Verify the behavior with different combinations of filters (FILTER_ORG_UNIT and FILTER_PE).

---

TESTS

• Added tests to validate the behavior of the period filter with single and multiple values.
• Ensured proper handling when both pe and ou filters are applied together.
• Included a test to confirm period filter is omitted when empty
• Verified the generated iframeSrc matches the expected URL for all scenarios.

---

Known issues

• When using custom widgets installed on the dashboard, the widget cannot currently react to changes in the period (pe) filter. This limitation arises because the pe filter value isn't dynamically communicated to the widget. A follow-up issue may be required to address this behavior.

---

Screenshots

---

Example:
If the itemFilters contains:

{
    FILTER_ORG_UNIT: [{ id: 'ou1', path: '/root/ou1' }, { id: 'ou2' }],
    FILTER_PE: [{id:'THIS_MONTH'}, {id:'LAST_MONTH'}]
}

[KaiVandivier]

Thanks for opening this Edson! 🙏 The logic looks good 👍

There's some things we should do to clean up the PR before we ask analytics folks to review it:

1. Add a more descriptive PR name, using conventional commit style, like "feat: add filter period to iframe src for custom widgets"
2. In the description, some code block styling is wrapping the screenshots, so the images aren't visible -- move those screenshots out of the code block so they're easy to see
3. There are some erroneous changes in en.pot and FilterSelector.js -- remove those
4. I added some inline comments in the code -- if you use the GitHub interface to apply them, make sure to use commit messages that follow the conventional commit style (start with chore:/fix:/refactor:)

Thanks again for setting this up! Let me know if you have any questions 🙂

[jenniferarnesen]

Thank you for submitting this pull request. Could you please have a look at the unit tests in file __tests__/getIframeSrc.spec.js and add relevant tests for the new code including:

• only pe filter (including cases with just 1 and >1 filters)
• pe filter and ou filter

[jenniferarnesen]

Hi Edson,
There are lint failures. You can ignore the lint-commit error (unless you want to rebase and fix it that way) because we'll do a squash commit when the time comes and rewrite the commit message at that point. But the lint error has to be fixed.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud