Add TypeScript installation to Google Drive MCP setup script

## Issue Description

The Google Drive MCP server setup script fails when TypeScript is not installed globally. This violates the "spilled coffee principle" as it creates a dependency that's not explicitly handled by the setup process.

## Current Behavior

When running `setup-gdrive-mcp.sh`, the build step fails with:
```
sh: 1: tsc: not found
```

This happens because the build script for the Google Drive MCP server uses TypeScript to compile the code:
```
> @modelcontextprotocol/server-gdrive@2025.1.14 build
> tsc && shx chmod +x dist/*.js
```

## Proposed Solution

Modify the `setup-gdrive-mcp.sh` script to automatically install TypeScript if it's not already installed:

```bash
# Check if TypeScript is installed
if ! command -v tsc &> /dev/null; then
echo "TypeScript not found. Installing TypeScript..."
npm install -g typescript
fi
```

This change ensures that the setup process is self-contained and resilient, following the spilled coffee principle by handling all dependencies automatically.

## Benefits

- Improves user experience by eliminating manual dependency installation
- Makes the setup process more robust and less error-prone
- Follows the spilled coffee principle by ensuring the system can recover from unexpected states
- Maintains consistency with other MCP server setup scripts

## Additional Context

This issue was discovered during testing of the Google Drive MCP integration. The TypeScript dependency is required for building the server from source.

Start by reading setup-gdrive-mcp.sh and identify where the Google Drive MCP server build runs. Reproduce the setup with TypeScript unavailable globally, then verify that the script completes the build successfully without manual installation. Done means the tsc: not found failure is handled during setup.

Written by the indexing model from the issue text.