Bump CI retention days

[matthiasdiener]

Description

To make it faster and easier to rerun intermittent failing tests.

Type of change

• Documentation change (change only to the documentation, either a fix or a new content)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Infra/Build change
• Code refactoring

Changes

Please list the changes introduced in this PR:

• Change A
• Change B

Checklist:

• I have read and followed the contributing guidelines
• The functionality is complete
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[ipanfilo]

It is made 1 day because of size of artifact and limited storage. It has to be confirmed with enterprise admins that we have enough space to store 7N750Mb data. Even after CK_JIT adoption it will be 7N320Mb that will probably be good for 3 day comparing to original (before QoLA) 1Gb package size.

[matthiasdiener]

It is made 1 day because of size of artifact and limited storage. It has to be confirmed with enterprise admins that we have enough space to store 7_N_750Mb data. Even after CK_JIT adoption it will be 7_N_320Mb that will probably be good for 3 day comparing to original (before QoLA) 1Gb package size.

Understood. My impression was that since this is a public repo with artifact storage on GitHub's servers, no quota applies (see e.g. https://docs.github.com/en/actions/concepts/billing-and-usage#about-billing-for-github-actions). But would be good to double check with the admins.