Reorganize Lucky Parking GitHub teams and repository access

### Description

With assistance from Hack for LA organization administrators, replace the current confusing Lucky Parking team structure with a clear, least-privilege hierarchy that matches functional responsibilities and supports future ownership and review routing.

### Action Items

- [ ] Coordinate with the [admin team](https://hackforla.slack.com/archives/C01Q24YF56J/p1789502318408459) to re-organize Lucky Parking teams on GitHub.
- [ ] Audit current direct and inherited team membership, team maintainers, repository roles, and pending invitations.
- [ ] Confirm the target hierarchy and repository roles:

```
lucky-parking (role: read)
├── lucky-parking-admin (role: admin)
├── lucky-parking-eng (role: write)
├── lucky-parking-data (role: write)
├── lucky-parking-design (role: write)
├── lucky-parking-product (role: triage)
└── lucky-parking-write (DELETE)
└── lucky-parking-merge (DELETE)
```

### Additional Information

Status: Triage — requires organization-admin assistance and confirmation of membership, responsibility, and repository access before execution.

Why this structure: child teams inherit their parent team's repository access. The `lucky-parking` parent therefore remains read-only (safe for every child); engineering, data, and design inherit write through `lucky-parking-write`; product receives triage without write access; and the admin team receives explicit admin access.