refactor: refactor vacuum

[drmingdrmer]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

refactor: refactor vacuum

Tests

• Unit Test
• Logic Test
• Benchmark Test
• No Test - Explain why

Type of change

• Refactoring

Related Issues

---

This change is 

[what-the-diff]

PR Summary

• Altered Behaviour for Duplicate Entries
  The UpsertTableCopiedFileReq has been updated in various places to replace fail_if_duplicated: true with insert_if_not_exists: true. This reflects a change in dealing with duplicate entries, with an emphasis on inserting new entries only when they don't already exist.

• Formatted Output for the TableCopiedFileNameIdent Struct
  We've added a new implementation of the fmt::Display trait for the TableCopiedFileNameIdent struct. This will now enable a formatted output for its items improving readability and debuggability of code.

• Field and Documentation Update in struct UpsertTableCopiedFileReq
  The UpsertTableCopiedFileReq struct has been modified to rename fail_if_duplicated field to insert_if_not_exists. Alongside the field name change, the corresponding documentation has been updated to clearly express that if true, existing keys will be ignored.

• Consistent Renaming Across Files
  To maintain consistency with the new field name and its intended functionality, all files where UpsertTableCopiedFileReq is defined or implemented have undergone appropriate changes.