Add option to filter packages by build time in CLM

[wweellddeerr]

What does this PR change?

It adds a new option to CLM, allowing users to filter packages by build date.

GUI diff

Before:

After:

• DONE

Documentation

• No documentation needed: add explanation. This can't be used if there is a GUI diff

• No documentation needed: only internal and user invisible changes

• Documentation issue was created: Link for SUSE Manager contributors, Link for community contributors.

• API documentation added: please review the Wiki page Writing Documentation for the API if you have any changes to API documentation.

• (OPTIONAL) Documentation PR

• DONE

Test coverage

• Unit tests were added

• DONE

Links

Fixes https://github.com/SUSE/spacewalk/issues/13350

• DONE

Changelogs

Make sure the changelogs entries you are adding are compliant with https://github.com/uyuni-project/uyuni/wiki/Contributing#changelogs and https://github.com/uyuni-project/uyuni/wiki/Contributing#uyuni-projectuyuni-repository

If you don't need a changelog check, please mark this checkbox:

• No changelog needed

If you uncheck the checkbox after the PR is created, you will need to re-run changelog_test (see below)

Re-run a test

If you need to re-run a test, please mark the related checkbox, it will be unchecked automatically once it has re-run:

• Re-run test "changelog_test"
• Re-run test "backend_unittests_pgsql"
• Re-run test "java_pgsql_tests"
• Re-run test "schema_migration_test_pgsql"
• Re-run test "susemanager_unittests"
• Re-run test "javascript_lint"
• Re-run test "spacecmd_unittests"

[github-actions]

Suggested tests to cover this Pull Request

• srv_add_rocky8_repositories
• srv_rename_hostname
• allcli_sanity
• allcli_update_activationkeys
• srv_monitoring
• proxy_branch_network
• proxy_cobbler_pxeboot

[cbbayburt]

Hi @wweellddeerr,
We've had some discussions about the requirements for this, and here's what we've come up with:

Using multiple sources for the date will be ultimately confusing for the user so for this filter we should use only the build date and not fall back to the created date or anything else.

To convey this properly, we should change all the UI and code occurrences of "package issue date" or "issue date" to just "Package (Build Date)" or "build date", etc.

[github-actions]

👋 Hello! Thanks for contributing to our project.
Acceptance tests will take some time (aprox. 1h), please be patient ☕
You can see the progress at the end of this page and at https://github.com/uyuni-project/uyuni/pull/7582/checks
Once tests finish, if they fail, you can check 👀 the cucumber report. See the link at the output of the action.
You can also check the artifacts section, which contains the logs at https://github.com/uyuni-project/uyuni/pull/7582/checks.

If you are unsure the failing tests are related to your code, you can check the "reference jobs". These are jobs that run on a scheduled time with code from master. If they fail for the same reason as your build, it means the tests or the infrastructure are broken. If they do not fail, but yours do, it means it is related to your code.

Reference tests:

• https://github.com/uyuni-project/uyuni/actions/workflows/acceptance_tests_secondary_parallel.yml?query=event%3Aschedule

• https://github.com/uyuni-project/uyuni/actions/workflows/acceptance_tests_secondary.yml?query=event%3Aschedule

For more tips on troubleshooting, see the troubleshooting guide.

Happy hacking!
⚠️ You should not merge if acceptance tests fail to pass. ⚠️

[wweellddeerr]

Hi @wweellddeerr, We've had some discussions about the requirements for this, and here's what we've come up with:

Using multiple sources for the date will be ultimately confusing for the user so for this filter we should use only the build date and not fall back to the created date or anything else.

To convey this properly, we should change all the UI and code occurrences of "package issue date" or "issue date" to just "Package (Build Date)" or "build date", etc.

Changed, accordingly.

[cbbayburt]

Thanks very much @wweellddeerr LGTM 👍

One minor thing:
This came from a Jira request, so you need to add the Jira tracker ID to the changelog entries like "(jsc#SUMA-282)" just like we do with the bsc#s