Persist and Display updated_by / updated_at for Cases Retention Policy

[sanjacornelius]

Issue & Reproduction Steps

This PR adds audit tracking for Cases Retention Policy configurations at the process level. Specifically, it persists the user and timestamp associated with retention policy updates and surfaces this information in the UI.

When a retention policy is modified and saved, the system now stores the metadata and displays a “Last Modified By” indicator to improve traceability and configuration transparency.

Solution

• Persist retention_updated_by and retention_updated_at in processes.properties
• Update the UI to display:
  - Last Modified By: [USER] [DATE_TIME]
  - Only when the retention policy value has been changed
• Ensure unrelated configuration updates do not modify retention audit metadata

How to Test

1. Confirm the appropriate .env variables for Cases Retention Policy are configured.
2. Navigate to a Process → Configuration → Cases Retention settings.
3. Observe the default helper text displayed beneath the retention selection field.
4. Change the retention value and click Save.
5. Verify the helper text updates to:
   Last Modified By: [USER] [DATE_TIME]
6. Modify a different, unrelated process configuration setting and save.
7. Confirm that Last Modified By does not change unless the retention policy itself is modified.

Related Tickets & Packages

• FOUR-29108
  ci:deploy

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube