### Is there an existing issue for this?

- [X] I have searched the existing issues

### Feature description

LocalStack should support Server-Side-Encryption for SQS if possible, or at least pretend it does so that scripts that assume this working against AWS don't break with LocalStack.

Currently terraform for example fails when trying to create an SQS queue with `sqs_managed_sse_enabled     = true` 

### 🧑‍💻 Implementation

It would probably be fine for now to at least simulate this in a basic `CRUD` way for at least the case when using AWS managed keys for the "encryption".


Example terraform:

```hcl
provider "aws" { 
  access_key                  = "test"
  secret_key                  = "test"
  region                      = "us-east-1"
  s3_force_path_style         = true
  skip_credentials_validation = true
  skip_metadata_api_check     = true
  skip_requesting_account_id  = true

  endpoints {
    sqs            = "http://localhost:4566"
    iam            = "http://localhost:4566"
  }
}

resource "aws_sqs_queue" "sqs" {
  name                        = "myq.fifo"
  fifo_queue                  = true
  content_based_deduplication = true
  sqs_managed_sse_enabled     = true
  
  tags = {
    service     = "myq"
  }
}
```

### Anything else?

- https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-configure-sqs-sse-queue.html
- https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-server-side-encryption.html
self,
        context: RequestContext,
        queue_url: String,
        entries: DeleteMessageBatchRequestEntryList,
    ) -> DeleteMessageBatchResult:
        """Deletes up to ten messages from the specified queue. This is a batch
        version of ``DeleteMessage.`` The result of the action on each message
        is reported individually in the response.
        Because the batch request can result in a combination of successful and
        unsuccessful actions, you should check for batch errors even when the
        call returns an HTTP status code of ``200``.
        Some actions take lists of parameters. These lists are specified using
        the ``param.n`` notation. Values of ``n`` are integers starting from 1.
        For example, a parameter list with two elements looks like this:
        ``&AttributeName.1=first``
        ``&AttributeName.2=second``
        :param queue_url: The URL of the Amazon SQS queue from which messages are deleted.
        :param entries: A list of receipt handles for the messages to be deleted.
        :returns: DeleteMessageBatchResult
        :raises TooManyEntriesInBatchRequest:
        :raises EmptyBatchRequest:
        :raises BatchEntryIdsNotDistinct:
        :raises InvalidBatchEntryId:
        """
        raise NotImplementedError
    @handler("DeleteQueue")
    def delete_queue(self, context: RequestContext, queue_url: String) -> None: