Mypy-boto3

Fixed
- `[types-aiobotocore]` `boto3.dynamodb.conditions.ConditionBase` import no longer fails if `boto3` is not installed

Notes

We are so close to **3 million** monthly downloads! To make this challenge a bit harder, this version drops outdated `py36` support. For good. It is now gone, it is not coming back. Please upgrade. I mean it.

Thank you as always for your bug reports and feature requests!

Changed
- `[boto3-stubs]` Dropped `py36` support
- `[types-aiobotocore]` Dropped `py36` support
- `[types-aioboto3]` Dropped `py36` support
- `[builder]` Added `LICENSE` file to all packages

Fixed
- `[botocore-stubs]` Removed `ETree` imports
- `[types-aiobotocore]` Imports from `boto3` and `aioboto3` are now safe in case libraries are not installed
- `[types-aioboto3]` Use `AIOBoto3ServiceResource` as a base class instead of `ServiceResource`
- `[types-aioboto3]` Use `AIOResourceCollection` as a base class instead of `ResourceCollection`

Fixed
- `[boto3-stubs]` `boto3.s3.transfer.create_transfer_manager` annotation was invalid (reported by kveretennicov in 156)
- `[types-s3transfer]` `fileobj` allows `IO | str | bytes` in all methods and functions (reported by kveretennicov in 155)
- `[boto3-stubs]` Removed useless `type: ignore` statements

Fixed
- `[types-aioboto3]` Lite version `Session.client` annotation was incorrect
- `[types-aiobotocore]` `args.ClientArgsCreator` annotation violated LSP
- `[types-aiobotocore]` `signers.AioS3PostPresigner` annotation violated LSP
- `[types-botocore]` Various small inconsistencies in annotations
- `[docs]` `Boto3 IDE` and `conda-forge` installation instructions removed from packages that do not support it

Notes

The second minor version bump in a row! This means that `types-aioboto3` is finally ready for production! `aioboto3` is fully annotated and supports implicit type annotations for all services, just like `boto3`!

- New `types-aioboto3` package (`boto3-stubs` alternative)
- New `types-aioboto3-lite` package (`boto3-stubs-lite` alternative)
- Automated checks for outdated stubs for `aioboto3` and `aiobotocore`

Added
- `[aioboto3]` New product `aioboto3` to build `types-aioboto3` and `types-aioboto3-lite` packages
- `[aioboto3]` New product `aioboto3-docs` to build `types-aioboto3` documentation
- `[check-stubs]` Support for `aiobotocore` package
- `[check-stubs]` Support for `aioboto3` package

Changed
- `[types-aioboto3]` Stubs updated to the latest `aioboto3` version
- `[types-aiobotocore]` Stubs updated to the latest `aiobotocore` version
- `[types-aiobotocore]` No longer directly depends on `aiobotocore`

Fixed
- `[check-stubs]` Relative paths in snapshots are replaced to avoid conflicts
- `[botocore-stubs]` Added compatibility with `types-aiobotocore`
- `[aiobotocore-docs]` Added annotations to usage examples

Notes

- `s3transfer` got its own stubs package
- `boto3-stubs` is finally cross-checked against the latest `boto3` version and is fully up-to-date
- `types-aiobotocore` uses correct `aiobotocore` classes alternatives
- Final preparations for `types-aioboto3` package release

Added
- `[s3transfer]` New `types-s3transfer` package that provides type annotations

Changed
- `[services]` All imports from `boto3`/`botocore`/`aiobotocore` retain their original names, `Boto3` prefix removed
- `[boto3-stubs]` Added dependency on `types-s3transfer`
- `[builder]` Type annotations processing memory usage decreased
- `[builder]` Refactored package post-processors to make `botocore`/`aiobotocore` separation cleaner
- `[builder]` Moved all static stubs to `stubs_static`
- `[ci]` New `check-stubs` script that covers `boto3`, `botocore` and `s3transfer` stubs

Fixed
- `[aiobotocore]` All `botocore` substitutes are replaced with proper `aiobotocore` alternatives (reported by carlos-alberto in 154)
- `[services]` `botocore.client.Client` usage replaced with `botocore.client.BaseClient`
- `[services]` Updated documentation links
- `[services]` Stubs-only packages have `Typing :: Stubs Only` classifier
- `[boto3-stubs]` Updated to the latest `boto3` version
- `[builder]` External imports were hashed incorrectly, potentially clashed