Send Webhooks (all) to Amazon SQS

Looking at the overall landscape of how we want the BOT to work, I think it would work well to have all webhooks sent to Amazon SQS (FIFO Queue). So that (1) we can ensure that if the BOT is down it will still get the messages, (2) we can conserve API calls, (3) we can do more faster processing (since we don't need to worry about API limits, and (4) we can negate the need for a public and private bot instance.

Webhooks should be able to be sent directly to SQS, however if not I would suggest that a simple AWS Lambda script will work.

Costs seem to be minimal:
SQS -> $0.50 per 1 million requests after the first 1 million
Data -> $0.90 per GB after first GB

IF we need Lambda the cost is: $0.20 per 1 million requests after the first million.

So, the thought would be have all webhooks for all the repos go to SQS, and then the BOT can pull from SQS at a time period that we select, I would go with every 3 minutes.

No files, tests, or entry points are named. Start by tracing the existing webhook delivery path and assessing whether direct Amazon SQS delivery or an AWS Lambda intermediary is feasible. Done means webhooks from all repositories reach an SQS FIFO queue and the bot can retrieve them on the proposed schedule.

Written by the indexing model from the issue text.