What problem does this PR solve?

Issue Number: close #10109

What is changed and how it works?

Add two parameters to control the cleaning behavior of expired files, for example:

1. To keep one day's files and clean them at 18 o 'clock every day, users can use the following configuration.

[sink.cloud-storage-config]
file-expiration-days = 1
# Second | Minute | Hour | Dom | Month | DowOptional
file-cleanup-cron-spec = "0 18 * * * *"    

2. To keep files for a week and clean them every Monday at 2 am, you can use the following configuration.

[sink.cloud-storage-config]
file-expiration-days = 7
# Second | Minute | Hour | Dom | Month | DowOptional
file-cleanup-cron-spec = "0 2 * * * 1"

3. The default configuration is

[sink.cloud-storage-config]
file-expiration-days = 0 # The default congiuration
file-cleanup-cron-spec = "0 2 * * * *"

• By default, files are not cleaned.
• If only the file-expiration-days is configured, then by default cdc will clean files at 2 a.m. each day.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Questions

Will it cause performance regression or break compatibility?

Do you need to update user documentation, design documentation or monitoring documentation?

Release note

`Add file-expiration-days and file-cleanup-cron-spec configurations for storage sink to control the cleaning behavior of expired files`.