Tomodachi

- Fix for an issue where a wrapped function is used as a handler function, which would then cause the keyword argument provided transport values to rely on the keyword arguments from the *wrapped function's* signature to be used instead of the keyword arguments from the *wrapper function's* signature.

The bug was found to be present since the last release, which included major refactoring of the *keyword argument provided transport values* functionality.

- The middleware execution logic has been improved to handle different argument types and edge cases more smoothly. Enhanced the way arguments are passed to middlewares and handlers, allowing better flexibility.

- Resolved an edge case where a service could end up calling `SNS.CreateTopic` numerous times due to thousands of messages simultanously being published to a topic that were previously unknown to the service.

- The `aws_sns_sqs_publish` function will now return the SNS message identifier as a `str` value if it is called with `wait=True` (default), or instead return an `asyncio.Task` object if called with `wait=False`.

- Function handlers, middlewares and envelopes can all now specify additional keyword arguments in their signatures and receive transport centric values.

Previously a few of these keyword values could be used for function handlers or envelopes, but not within middlewares. With this update the following keywords can be used across all kind of handler functions to allow for more flexibility in how to structure apps, logging, tracing, authentication, etc.

**Category: AWS SNS+SQS related values**

Use the following keywords arguments in function signatures (for handlers, middlewares and envelopes used for AWS SNS+SQS messages).

| | |
|:---|:---|
| `message_attributes` | Values specified as message attributes that accompanies the message body and that are among other things used for SNS queue subscription filter policies and for distributed tracing.
| `queue_url` | Can be used to modify visibility of messages, provide exponential backoffs, move to DLQs, etc.
| `receipt_handle` | Can be used to modify visibility of messages, provide exponential backoffs, move to DLQs, etc.
| `approximate_receive_count` | A value that specifies approximately how many times this message has been received from consumers on `SQS.ReceiveMessage` calls. Handlers that received a message, but that doesn't delete it from the queue (for example in order to make it visible for other consumers or in case of errors), will add to this count for each time they received it.
| `topic` | Simply the name of the SNS topic. For messages sent directly to the queue (for example via `SQS.SendMessage` API calls), instead of via SNS topic subscriptions (`SNS.Publish`), the value of `topic` will be an empty string.
| `sns_message_id` | The message identifier for the SNS message (which is usually embedded in the body of a SQS message). Ths SNS message identifier is the same that is returned in the response when publishing a message with `SNS.Publish`. The `sns_message_id` is read from within the `"Body"` of SQS messages, if the message body contains a message that comes from an SNS topic subscription.
| `sqs_message_id` | The SQS message identifier, which naturally will differ from the SNS message identifier as one SNS message can be propagated to several SQS queues. The `sqs_message_id` is read from the `"MessageId"` value in the top of the SQS message.
| `message_timestamp` | A timestamp of when the original SNS message was published.

**Category: "HTTP related values"**

Use the following keywords arguments in function signatures (for handlers and middlewares used for HTTP requests).

| | |
|:---|:---|
| `request` | The `aiohttp` request object which holds functionality for all things HTTP requests.
| `status_code` | Specified when predefined error handlers are run. Using the keyword in handlers and middlewares for requests not invoking error handlers should preferably be specified with a default value to ensure it will work on both error handlers and request router handlers.
| `websocket` | Will be added to websocket requests if used.

- Fixes an issue in the internal retry logic when using `aws_sns_sqs_publish` if calls to the AWS API `SNS.Publish` would intermittently respond with 408 response without any body, which previously would've resulted in a `AWSSNSSQSException("Missing MessageId in response")` immediately without retries.

This was previously attempted to be fixed in the 0.23.0 release, but instead fell through to become an exception with the `"Missing MessageId in response"` message instead.

The publish function will now catch exceptions from `botocore` of type `ResponseParserError` to which `botocore` has added that `"Further retries may succeed"`. `tomodachi` will retry such `SNS.Publish` calls up to 3 times and if after all retries the library will reraise the exception from `botocore`.

It seems that `botocore` does not automatically retry such errors itself.

- Similar to the above, the same kind of retries will now also be done during AWS API calls for `SQS.DeleteMessage`, where the `botocore.parser.QueryParser` would raise an `ResponseParserError` exception on 408 responses without body.

- Fixes typing syntax for compatibility with Python 3.8 and Python 3.9 to solve the incompatibility for Python 3.8 and Python 3.9 introduced in the the 0.24.1 release.
- Fixes an issue with an AWS SQS queue's message retention period attribute using an incompatible default value for FIFO queues.
- Support for `aiobotocore` 2.5.x releases.
- README.rst fixes to conform with RST format. (github: **navid-agz**)

- Adds max number of messages that the service will consume when using AWS SNS+SQS handlers configurable. (github: **navid-agz**)
- Changed default retention period of dead-letter-queues on AWS SNS+SQS. (github: **PabloAJomer**)

- `cchardet` is no longer a direct dependency to `tomodachi` on Python 3.10 and Python 3.11. If you want to use it, you must install it separately, which may require additional build tools when installing on Python 3.10+.
- Updates to the internal `tomodachi.envelope.ProtobufBase` envelope to now also support protobuf Python bindings versioned \>=4.0.0, when running with the (new default) `PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=upb` as `upb` slightly differs in representation of a Message type in relation to `cpp` and `python` implementations.
- Python 3.11 added to test matrix and trove classifiers to officially claim support.