fix: update retention rule for CLOUD and OSS

[NguyenHoangSon96]

Closes #1607

Fix the bug when updating the retention period of buckets:

• Before fix: set a retention period, eg. 1 hour, then change to never -> the retention period is still 1 hour
• After fix: set a retention period, eg. 1 hour, then change to never -> the retention period changes to never

The recorded screen is the result when update in OSS:

Screen.Recording.2025-02-25.at.15.18.00.mov

The image is the result when update in CLOUD:

Note: I have to mock the variable CLOUD because I don't know how to run the CLOUD in my local. In the captured screen the retentionRules in the payload is not exists when send to the backend like ui team suggested

Checklist

Authors and Reviewer(s), please verify the following:

• A PR description, regardless of the triviality of this change, that communicates the value of this PR
• Well-formatted conventional commit messages that provide context into the change
• Documentation updated or issue created (provide link to issue/PR)
• Signed CLA (if not already signed)
• Feature flagged, if applicable

[wdoconnell]

Thanks for doing this: I have one suggestion about how to convert this to a ternary. Otherwise, it looks good to me. Let me confer with the folks working on the OSS backend to ensure the OSS-specific change is correct.

[NguyenHoangSon96]

Hi @wdoconnell. Thank for the review
I fixed all things you mentioned
Please check again

[wdoconnell]

This looks good now from a UI perspective.

Please wait on a review from folks who are closer to the OSS for a backend approval.

FYI @davidby-influx: this is the PR handed off from @philjb in Slack.

[devanbenz]

LGTM just a comment about the linter changes