[Extensibility Request]: Add DriveId overloads for SharePoint Graph Client drive item operations

Describe the issue

The SharePoint Graph Client currently exposes a mix of DriveId-aware and default-drive-only operations.
The following methods already support targeting a specific drive:

• GetDrive()
• UploadFile()
• UploadLargeFile()
• CreateFolder()
  However, most drive item operations only work against the site's default drive (e.g. DownloadFile() or DeleteItem()). This makes it difficult to work with SharePoint sites containing multiple document libraries.

Expected behavior

Drive item operations should expose overloads that allow callers to explicitly work against a specific DriveId, similar to the existing UploadFile(), UploadLargeFile() and CreateFolder() APIs.

Steps to reproduce

1. Create a SharePoint site containing multiple document libraries.
2. Retrieve a non-default drive using GetDrives().
3. Upload content to the non-default drive using UploadFile(DriveId, ...).
4. Attempt to perform follow-up operations such as DownloadFile() or ItemExists() against the same drive.

The current API only exposes default-drive implementations for many drive item operations, making it impossible to continue working with the non-default drive through the SharePoint Graph Client.

Additional context

No response

I will provide a fix for a bug

• I will provide a fix for a bug

Start by comparing the existing DriveId-aware GetDrive(), UploadFile(), UploadLargeFile(), and CreateFolder() APIs with default-drive operations such as DownloadFile(), DeleteItem(), and ItemExists(). Trace the SharePoint Graph Client entry points and identify the remaining drive item operations that lack DriveId overloads. Done means those operations can target a non-default drive consistently with the existing APIs, with relevant tests updated or added if the repository provides them.