Google Drive connector: no granular editing for Docs and Sheets

The Google Drive connector exposes `read_file_content`, `create_file` and `update_file`, but `update_file` works at the whole-file level. There is no way to:

- write a value into a specific cell or range of a Google Spreadsheet
- append rows to a sheet
- replace or insert a specific paragraph or section in a Google Doc without rewriting the document

In practice this makes the connector read-only for native Google formats. Any edit means regenerating the entire document, which risks losing formatting, comments, named ranges, conditional formatting and revision history.

This is a common workflow for non-engineering users: a spreadsheet that gets updated weekly, a doc that gets a new section appended. Today the only workaround is driving the browser UI, which is slow and fragile.

Requested: a native Google Sheets connector with range-level read/write (values.get / values.update / values.append) and a Google Docs connector with the batchUpdate primitives (insert text, replace text, delete range).

Start by locating the existing Google Drive connector and its update_file implementation. Review how connector actions map to Google APIs, then assess the requested Sheets values.get, values.update, values.append and Docs batchUpdate operations. Done means native Sheets range editing and Docs text insertion, replacement, and deletion are supported without rewriting whole files.

Written by the indexing model from the issue text.