Limit background expiry to the API.

Using requests to drive background work (expiring things, mainly) is a hack to avoid the complexity of background workers, but it's reaching its limits. In the live deployment at `hi.grimoire.ca`, we found that requests for the UI were taking 300+ milliseconds as the expiry process required database access. The DB there is slow, which is a separate issue, but also being accessed many times for little benefit.

Since only the API is actually _affected_ by expiry, I've scoped the middleware down to just those endpoints.

0 files changed, 0 insertions, 0 deletions