### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current Behavior

Adding a binary message attribute to an SQS message results in a 500 Internal Error due to a `exception during call chain: Incorrect padding` error:
```
2022-12-21T15:56:38.698  INFO --- [   asgi_gw_2] localstack.request.aws     : AWS sqs.SendMessage => 500 (InternalError)
2022-12-21T15:56:41.701 ERROR --- [   asgi_gw_2] l.aws.handlers.logging     : exception during call chain: Incorrect padding
```

The binary data (hex encoded) is:
```
7472616365706172656E741E30302D39613235616632623863356336353937383338383830316165353633313736622D616331393436313566356662326561662D3031
```

This is UTF-8/ASCII text but with one control character in it (`0x1E`), but the presence of the control character seems immaterial - the problem remains when this is  swapped out for a printable character.

Swapping out localstack for netcat in order to observe the actual posted data (note the data is slightly different as it is random each time):
```
Host: localhost:6565
User-Agent: aws-sdk-go-v2/1.17.3 os/linux lang/go/1.18.4 md/GOOS/linux md/GOARCH/amd64 api/sqs/1.19.17
Content-Length: 335
Amz-Sdk-Invocation-Id: 8e51778c-8aca-4ea9-ae5a-3d36f80b6f19
Amz-Sdk-Request: attempt=1; max=3
Authorization: AWS4-HMAC-SHA256 Credential=1234/20221221/us-east-1/sqs/aws4_request, SignedHeaders=amz-sdk-invocation-id;amz-sdk-request;content-length;content-type;host;x-amz-date, Signature=5312bc321178fe3deaac7426c1d3276139ed4a404cc39261d4324e5becdda380
Content-Type: application/x-www-form-urlencoded
X-Amz-Date: 20221221T191345Z
Accept-Encoding: gzip

Action=SendMessage&MessageAttribute.1.Name=OTEL&MessageAttribute.1.Value.BinaryValue=dHJhY2VwYXJlbnQeMDAtNzc0MDYyZDZjMzcwODFhNWEwYjliNWI4OGUzMDYyN2MtMmQyNDgyMjExZjY0ODlkYS0wMQ%3D%3D&MessageAttribute.1.Value.DataType=Binary&MessageBody=Hello+World%21&QueueUrl=http%3A%2F%2Flocalhost%3A6565%2F000000000000%2Ftest-queue&Version=2012-11-05
```

Decoding the URL-encoded base64 data, it looks OK to me:
```
dHJhY2VwYXJlbnQeMDAtNzc0MDYyZDZjMzcwODFhNWEwYjliNWI4OGUzMDYyN2MtMmQyNDgyMjExZjY0ODlkYS0wMQ==
```

And back to binary looks OK:

```
echo 'dHJhY2VwYXJlbnQeMDAtNzc0MDYyZDZjMzcwODFhNWEwYjliNWI4OGUzMDYyN2MtMmQyNDgyMjExZjY0ODlkYS0wMQ==' | base64 -d | od -A x -t x1z -v --endian=big
000000 74 72 61 63 65 70 61 72 65 6e 74 1e 30 30 2d 37  >traceparent.00-7<
000010 37 34 30 36 32 64 36 63 33 37 30 38 31 61 35 61  >74062d6c37081a5a<
000020 30 62 39 62 35 62 38 38 65 33 30 36 32 37 63 2d  >0b9b5b88e30627c-<
000030 32 64 32 34 38 32 32 31 31 66 36 34 38 39 64 61  >2d2482211f6489da<
000040 2d 30 31                                         >-01<
```

```
>>> data='dHJhY2VwYXJlbnQeMDAtNzc0MDYyZDZjMzcwODFhNWEwYjliNWI4OGUzMDYyN2MtMmQyNDgyMjExZjY0ODlkYS0wMQ=='
>>> import base64
>>> binarydata = base64.b64decode(data)
>>> print(binarydata)
b'traceparent\x1e00-774062d6c37081a5a0b9b5b88e30627c-2d2482211f6489da-01'
```

Conclusion: Nothing seems to be wrong with the base64 padding in the URL parameter.

This works fine against real AWS.

### Expected Behavior

Binary Message Attributes to be successfully accepted by Localstack SQS.

### How are you starting LocalStack?

With the `localstack` script

### Steps To Reproduce

#### How are you starting localstack (e.g., `bin/localstack` command, arguments, or `docker-compose.yml`)

    localstack start

#### Client commands (e.g., AWS SDK code snippet, or sequence of "awslocal" commands)

    


### Environment

```markdown
- OS:NAME="Ubuntu"
     VERSION="20.04.4 LTS (Focal Fossa)"
- LocalStack: 1.3.1
```


### Anything else?

_No response_
with pytest.raises(ClientError) as e:
            message_attributes = {"k": {"DataType": "String", "StringValue": "x"}}
            message_attributes_size = len("k") + len("String") + len("x")
            message_body = "a" * (DEFAULT_MAXIMUM_MESSAGE_SIZE - message_attributes_size)
            sqs_client.send_message_batch(
                QueueUrl=sqs_queue,
                Entries=[
                    {
                        "Id": "1",
                        "MessageBody": message_body,
                        "MessageAttributes": message_attributes,
                    },
                    {"Id": "2", "MessageBody": "a"},
                ],
            )
        snapshot.match("send_oversized_message_batch", e.value.response)
    @pytest.mark.aws_validated
    @pytest.mark.skip_snapshot_verify(paths=["$..Error.Detail"])
    def test_send_message_batch_with_oversized_contents_with_updated_maximum_message_size(