[Iceberg] Support procedure remove_orphan_files

[hantangwangd]

Description

This PR support the procedure remove_orphan_files for iceberg. It can be used to remove files which are not referenced in any metadata files of an Iceberg table and can thus be considered "orphaned".

See examples as follow:

• Remove any files which are not known to the table db.sample and older than specified timestamp::

CALL iceberg.system.remove_orphan_files('db', 'sample', TIMESTAMP '2023-08-31 00:00:00.000');

• Remove any files which are not known to the table db.sample and created 3 days ago (by default)::

CALL iceberg.system.remove_orphan_files(schema => 'db', table_name => 'sample');

Motivation and Context

Support removing orphan files that are not referenced in any metadata files for Iceberg

Test Plan

• Newly added test cases in TestRemoveOrphanFilesProcedure

Contributor checklist

• Please make sure your submission complies with our development, formatting, commit message, and attribution guidelines.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

== RELEASE NOTES ==


Iceberg Connector Changes
* Add procedure `remove_orphan_files` to remove orphan files that are not referenced in any metadata files for Iceberg. :pr:`23267`

[kiersten-stokes]

This will be nice to have! Just NITs from me

[steveburnett]

Thanks for the doc! Local doc build with the new table looks good. A minor suggested rephrase for active voice, and shortening for readability.

[steveburnett]

LGTM! (docs)

Pull updated branch, new local docs build, looks good. Thanks!

[ZacBlanco]

A few initial comments. Great to see us getting more parity with Iceberg's Spark procedures

[ZacBlanco]

Two final things. Also, I would like to see a test which exercises the default expiry limit. I don't have a good idea on how to do that in a reasonable time frame within the test, so I am happy to leave as is if you think it would be difficult

[hantangwangd]

I would like to see a test which exercises the default expiry limit. I don't have a good idea on how to do that in a reasonable time frame within the test, so I am happy to leave as is if you think it would be difficult

Seems it's indeed a bit difficult to test this scenario unless we change the implementation of remove_orphan_files to support configuring the default value of older_than. I'm not so sure if it's worthing do this. Maybe we can supplement such test cases when we figure out a better time test frame?