Journal retains some backups that have expired for a long time

**BUG REPORT**

***Describe the bug***

1. We have a bookie work environment, which is deployed with other services mixed together.
2. Machine disk space allocation is relatively tight.
3. Bookie is not always in traffic mode, sometimes it has short traffic write peaks, sometimes it is always idle.
4. We hope that when the traffic peaks, a few more journal file backups can help us restore the bookie in abnormal situations, but we also hope that when the traffic is low, we can clean up the journal files that have been backed up for a long time.

As shown in the figure below, the oldest journal file is already on June 23, 2022, and now it is December 20, and during this period, our bookie has been running, and these journals have existed for a long time along with the backup strategy.


We can add a retention mechanism about time to help us guarantee the requirement of point 4.