Add /next-hour endpoint

[ebanner]

In order to have 60 minute event reminders (TampaDevs/events-slack-push#2), this PR adds a /next-hour endpoint to show meetups happening in the next hour

[ebanner]

Closing because it seems unnecessary to add an endpoint since we're hitting the API pretty infrequently and we can just do the filtering on the ruby/client side

[chtzvt]

@ebanner I agree with your previous comment, but I do think that date-based filters would be a useful addition to the API.

That said, I would recommend a slightly modified approach to what was included in this PR-- rather than a single endpoint that can be only for a particular use case (events within the next hour), what I'd prefer to see would look like a pair of query parameter filters:

• within_hours: Specifies an integer number of hours that upcoming events must fall within (the next 1 hour, the next 48 hours, etc), and
• within_days: Specifies an integer number of days to filter the upcoming events list.

With these:

• The upcoming hourly event reminders are satisfied:
  • https://events.api.tampa.dev/?within_hours=1
• So too are the weekly summaries:
  • https://events.api.tampa.dev/?within_days=14

This not only satisfies the original use case, but it also provides a pretty flexible utility filter that lets downstream consumers avoid doing at least some (if not most of) the date-based filtering themselves.