feat(api): Support specifying file system for more APIs

[Eyizoha]

Purpose

Currently, most APIs require specifying the file system through the Options::FILE_SYSTEM configuration. Even when using a single file system (which should be the primary use case, as cross-file-system tables are quite rare), the implementation still uses ResolvingFileSystem as a forwarding layer. This introduces overhead on every file system access: parsing the path to extract the scheme, acquiring a read lock to obtain the actual underlying file system, and forwarding operations. Creating file systems via Options and forwarding through ResolvingFileSystem introduces unnecessary file system instances and computational overhead.

This change adds methods or parameters to directly specify file system instances for most APIs that require file system operations. This allows external systems to reuse existing file system instances and bypass the forwarding layer, addressing the issues mentioned above.

Tests

Modified existing unit tests to cover the API changes

API and Format

Yes - API Enhancement (Backward Compatible)
Changes to APIs in include/:

• Added WithFileSystem() methods to builder classes
• Added file_system parameters (with nullptr default values) to function signatures
• When file system is not explicitly provided, behavior is unchanged from before

Documentation

None

[lxy-9602]

+1