Tables: 1Password Vault Access API

### Overview
We need to deploy a Node.js REST API to the HFLA Incubator that automates 1Password vault access management. This API is used by our Google Apps Script onboarding system to automatically grant/revoke vault access when members join or leave projects.
Related Issue: https://github.com/hackforla/tables/issues/137

#### Application Stack

| Component | Details |
|-----------|---------|
| Runtime | Node.js 18 |
| Framework | Express.js |
| Dependencies | 1Password CLI v2 (must be installed in container) |
| Port | 3000 |
| Health Check | `GET /health` |

#### Resource Requirements

| Resource | Value | Notes |
|----------|-------|-------|
| CPU | 256 (0.25 vCPU) | Minimal, mostly I/O bound |
| Memory | 512 MB | Should be sufficient |
| Instances | 1 | No scaling needed |
| Storage | None | Stateless |

#### Secrets Required

We need to store these secrets in AWS Secrets Manager:

| Secret Name | Description |
|-------------|-------------|
| `API_KEY` | API authentication key |
| `OP_BOT_PASSWORD` | 1Password bot account password |
| `OP_BOT_SECRET_KEY` | 1Password secret key (A3-XXXXX format) |

### Questions
1.What's the deployment workflow? Do we need to create a separate repo?
2.Is there a standard pattern for API-only deployments in the Incubator?

### Action Items

### Resources/Instructions

Start by reviewing related issue #137 and existing API-only deployment patterns in the hackforla/devops repository. Determine whether a separate repository is needed and how the Node.js 18, Express.js, 1Password CLI, health check, and AWS Secrets Manager requirements fit the deployment workflow. Done means the workflow and standard deployment pattern are documented or agreed upon.

Written by the indexing model from the issue text.