[Feature] Instantiate DataLakeFileClient in AdlsStorageClient

Nobody has claimed this yet.

### Feature Request Proposal

Now, `DataLakeFileClient` is defaulted to `null` in `AdlsStorageClient`. The goal is to instantiate The DLFC using methods found in the `ADLSFileIO` class.

### Motivation

> #### What is the use case for this feature?
Used for future operations that require client access.

### What component(s) does this feature affect?

- [ ] `Table Service`: This is the RESTful catalog service that stores table metadata. `:services:tables`
- [ ] `Jobs Service`: This is the job orchestrator that submits data services for table maintenance. `:services:jobs`
- [ ] `Data Services`: This is the jobs that performs table maintenance. `apps:spark`
- [X] `Iceberg internal catalog`: This is the internal Iceberg catalog for OpenHouse Catalog Service. `:iceberg:openhouse`
- [ ] `Spark Client Integration`: This is the Apache Spark integration for OpenHouse catalog. `:integration:spark`
- [ ] `Documentation`: This is the documentation for OpenHouse. `docs`
- [ ] `Local Docker`: This is the local Docker environment for OpenHouse. `infra/recipes/docker-compose`
- [ ] `Other`: Please specify the component.

### Details

_No response_

Start by reading AdlsStorageClient and the client-construction methods in ADLSFileIO. Trace how the DataLakeFileClient is currently represented and verify the expected client access for future operations. Done means the client is instantiated through the existing ADLSFileIO methods and the relevant Iceberg internal catalog behavior remains functional.

Written by the indexing model from the issue text.