feat: add new endpoints to change log retention for exps and trials [DET-9995]

[salonig23]

Description

Added new API Endpoints, CLI commands and WebUI elements to change log retention for experiments and trials

Test Plan

• Added integration tests to test the API

For CLI -
Experiment:

1. Create an experiment.
2. Wait for the experiment to complete.
3. Run det e set log-retention-days <exp-id> --days 50
4. Check the tasks table in the database to see if the associated tasks for the experiment have updated the log retention days to 50.
5. Run det e set log-retention-days <exp-id> --days none --forever
6. Check the tasks table in the database to see if the associated tasks for the experiment have updated the log retention days to -1.

Trial:

1. Create an experiment.
2. Wait for the experiment to complete.
3. Run det t set log-retention-days <trial-id> --days 50 for any trial in the experiment.
4. Check the tasks table in the database to see if the associated tasks for the trial have updated the log retention days to 50.
5. Run det t set log-retention-days <trial-id> --days none --forever
6. Check the tasks table in the database to see if the associated tasks for the trial have updated the log retention days to -1.

For API -

1. Create an experiment.
2. Wait for the experiment to complete.
3. Use the following API endpoint:

curl -X 'PUT'
'http://localhost:8080/api/v1/experiments/1/retain_logs'
-H 'accept: application/json'
-H 'Content-Type: application/json'
-d '{
"experimentId": 1,
"numDays": 40
}'

Check the tasks table in the database to see if the associated tasks for the experiment have updated the log retention days to 40.

curl -X 'PUT'
'http://localhost:8080/api/v1/trials/1/retain_logs'
-H 'accept: application/json'
-H 'Content-Type: application/json'
-d '{
"trialId": 1,
"numDays": -1
}'

Check the tasks table in the database to see if the associated tasks for the trial have updated the log retention days to -1.

For WebUI -

1. Create a few experiments.
2. Go to the Experiments list in the Web UI and select a few of them and then click on the actions button.
   
3. Select the Retain Logs option from the drop down.
4. Type any number in the Number of days field when prompted.
5. Wait for a success message.
6. Check the tasks table in the database to see if the associated tasks for the experiment have updated the log retention days to the number you put in.
7. Select a few more experiments and follow the above steps, but this time click on the 'Forever' checkbox instead.
8. Wait for a success message.
9. Check the tasks table in the database to see if the associated tasks for the experiment have updated the log retention days to -1.
10. Also check the Trial List Table to see if the Log Retention Days Column shows up and has the correct days.

Commentary (optional)

Checklist

• Changes have been manually QA'd
• User-facing API changes need the "User-facing API Change" label.
• Release notes should be added as a separate file under docs/release-notes/.
  See Release Note for details.
• Licenses should be included for new code which was copied and/or modified from any external code.

Ticket

DET-9995

[codecov]

Codecov Report

Attention: Patch coverage is 37.27455% with 313 lines in your changes are missing coverage. Please review.

Project coverage is 47.12%. Comparing base (53bf20e) to head (c2f5e39).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8982      +/-   ##
==========================================
- Coverage   52.04%   47.12%   -4.93%     
==========================================
  Files         750     1153     +403     
  Lines       80799   142358   +61559     
  Branches        0     2421    +2421     
==========================================
+ Hits        42053    67082   +25029     
- Misses      38746    75086   +36340     
- Partials        0      190     +190     

Flag	Coverage Δ
backend	42.92% <14.28%> (-0.13%)	⬇️
harness	64.24% <37.37%> (+2.25%)	⬆️
web	38.95% <44.70%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
harness/determined/common/experimental/trial.py	55.60% <100.00%> (+0.21%)	⬆️
master/internal/trial.go	41.69% <100.00%> (+0.11%)	⬆️
master/test/olddata/pre_run_trials.go	100.00% <100.00%> (ø)
...ages/ExperimentDetails/ExperimentDetailsHeader.tsx	74.93% <100.00%> (ø)
...pages/ExperimentDetails/ExperimentTrials.table.tsx	99.00% <100.00%> (ø)
webui/react/src/services/apiConfig.ts	72.70% <100.00%> (ø)
webui/react/src/types.ts	99.66% <100.00%> (ø)
webui/react/src/utils/experiment.ts	83.66% <100.00%> (ø)
master/pkg/model/experiment.go	13.93% <0.00%> (-0.06%)	⬇️
webui/react/src/services/decoder.ts	19.93% <0.00%> (ø)
... and 15 more

... and 415 files with indirect coverage changes

[netlify]

✅ Deploy Preview for determined-ui ready!

Name	Link
🔨 Latest commit	c2f5e39
🔍 Latest deploy log	https://app.netlify.com/sites/determined-ui/deploys/6605cce3e95c9300087561e8
😎 Deploy Preview	https://deploy-preview-8982--determined-ui.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.