Support up-to-date `botocore`

[jakob-keller]

Description of Change

This PR intends to improve general compatibility of aiobotocore within the Python ecosystem by bumping the dependency specification of botocore, as well as boto3 and awscli.

It also restores feature parity with respect to recently released and improved AWS services, in particular adding support for S3 Express One Zone.

Assumptions

Upstream diff contains multiple changes that affect this codebase.

Checklist for All Submissions

• [x] I have added change info to CHANGES.rst
• [x] If this is resolving an issue (needed so future developers can determine if change is still necessary and under what conditions) (can be provided via link to issue with these details): closes #1065
  • [ ] Detailed description of issue
  • [ ] Alternative methods considered (if any)
  • [ ] How issue is being resolved
  • [ ] How issue can be reproduced
• [ ] If this is providing a new feature (can be provided via link to issue with these details):
  • [ ] Detailed description of new feature
  • [ ] Why needed
  • [ ] Alternatives methods considered (if any)

Checklist when updating botocore and/or aiohttp versions

• [x] I have read and followed CONTRIBUTING.rst
• [x] I have updated test_patches.py where/if appropriate (also check if no changes necessary)
• [x] I have ensured that the awscli/boto3 versions match the updated botocore version

[codecov[bot]]

Codecov Report

Attention: 23 lines in your changes are missing coverage. Please review.

Comparison is base (1ce6853) 86.46% compared to head (ef378b7) 86.13%.

Files	Patch %	Lines
aiobotocore/utils.py	45.16%	17 Missing :warning:
aiobotocore/signers.py	58.33%	5 Missing :warning:
aiobotocore/client.py	92.30%	1 Missing :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #1063 +/- ## ========================================== - Coverage 86.46% 86.13% -0.34% ========================================== Files 60 60 Lines 5814 5863 +49 ========================================== + Hits 5027 5050 +23 - Misses 787 813 +26 ``` | [Flag](https://app.codecov.io/gh/aio-libs/aiobotocore/pull/1063/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=aio-libs) | Coverage Δ | | |---|---|---| | [unittests](https://app.codecov.io/gh/aio-libs/aiobotocore/pull/1063/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=aio-libs) | `86.13% <58.92%> (-0.34%)` | :arrow_down: | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=aio-libs#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[jakob-keller]

@thehesiod: Another bump that adds support for new AWS services and features.

I'm unsure how to deal with the lack of test coverage. Is this something to be concerned about?

[thehesiod]

@thehesiod: Another bump that adds support for new AWS services and features.

I'm unsure how to deal with the lack of test coverage. Is this something to be concerned about?

not reaaaly, bonus if they're added. We should probably have a task to port all the botocore tests over

[thehesiod]

will get to this today

[jakob-keller]

will get to this today

I just pushed another update that extends compatibility up to yesterday's botocore release. It's all yours now ;-)

[thehesiod]

whoops didn't get to it. will do asap

[thehesiod]

going to do version w/o prefix this time, see how it goes

[thehesiod]

thanks for all the help!

[thehesiod]

I liked your strategy of supporting multiple botocore versions, probably worth adding to the docs describing how to do upgrades

[thehesiod]

actually was thinking about this last night, we can probably add a python helper where you set a base revision, and it tells you which ranges have only service json changes. Would save a lot of manual labor.

[jakob-keller]

we can probably add a python helper where you set a base revision, and it tells you which ranges have only service json changes.

That's true. To reach the next level of automation, it would be nice to run a scheduled GitHub action that checks for new botocore releases and opens PRs, if these are light-weight, i.e. only contain service JSON updates. Once that is stable, these PRs could even be auto-merged after passing CI. Eventually, we could also do automated minor releases.

[thehesiod]

i like your thinking :]