Implement TTL for History and Schedule Tables

# Why?

**As a** Backend Engineer

**I want** to limit the size of the tables

**So that** I can increase overall read latency

# What?

Implement TTL for the history table (and schedule table once we have that). Don't need to know the history past 3 months, so can just remove things. Maybe not necessary, but can create a Lambda function to do it, so that it preserves the history of the last return, so that we know who used it last essentially.