Force-remove mocks after tests to fix batcher invocation during deploy

[austinbyers]

After #28 introduced moto to the unit test framework, the batcher invocation during python3 manage.py deploy breaks with an error like the following:

requests.exceptions.ConnectionError: Connection refused: POST https://lambda.REGION.amazonaws.com/2015-03-31/functions/FUNCTION_NAME

Due to getmoto/moto#1026, moto mocks are not always restored correctly. This means that after the unit tests run, part of boto3 was still mocked out.

As a simple workaround, I've added a decorator which manually restores the underlying HTTPAdapter after running the unit test suite.

Other Minor Changes

• Fixes a link in README
• Fixes Dynamo metric alarm to reference generic ThrottledRequests instead of ReadThrottleEvents specifically

Tested

CI and deployed to an empty test account. Batcher invocation was successful during the test deploy.

Reviewers

to: @ryandeivert
cc: @airbnb/binaryalert-maintainers

[ryandeivert]

I assume you have, but did you try importing all of the the moto mocks as decorators, like:

from moto import mock_cloudwatch, mock_s3, mock_lambda, mock_sqs

and wrapping the whole MainTest class with them, like:

@mock_s3
@mock_sqs
@mock_lambda
@mock_cloudwatch
class MainTest(unittest.TestCase):
    ....

instead of instantiating them within the test case setup?

[ryandeivert]

I tested this quick and it doesn't seem to work either :)

[austinbyers]

Yep, I tried decorating individual tests, class-level, and explicit mock/unmock :(

[ryandeivert]

LGTM