### 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
For each message returned, the response includes the following:
        -  The message body.
        -  An MD5 digest of the message body. For information about MD5, see
           `RFC1321 <https://www.ietf.org/rfc/rfc1321.txt>`__.
        -  The ``MessageId`` you received when you sent the message to the
           queue.
        -  The receipt handle.
        -  The message attributes.
        -  An MD5 digest of the message attributes.
        The receipt handle is the identifier you must provide when deleting the
        message. For more information, see `Queue and Message
        Identifiers <https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-queue-message-identifiers.html>`__
        in the *Amazon SQS Developer Guide*.
        You can provide the ``VisibilityTimeout`` parameter in your request. The
        parameter is applied to the messages that Amazon SQS returns in the
        response. If you don't include the parameter, the overall visibility
        timeout for the queue is used for the returned messages. For more
        information, see `Visibility
        Timeout <https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-visibility-timeout.html>`__
        in the *Amazon SQS Developer Guide*.
        A message that isn't deleted or a message whose visibility isn't
        extended before the visibility timeout expires counts as a failed
        receive. Depending on the configuration of the queue, the message might
        be sent to the dead-letter queue.
        In the future, new attributes might be added. If you write code that
        calls this action, we recommend that you structure your code so that it
        can handle new attributes gracefully.
        :param queue_url: The URL of the Amazon SQS queue from which messages are received.
        :param attribute_names: A list of attributes that need to be returned along with each message.
        :param message_attribute_names: The name of the message attribute, where *N* is the index.