### 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
and is unique within the scope of your queues.
        After you create a queue, you must wait at least one second after the
        queue is created to be able to use the queue.
        To get the queue URL, use the ``GetQueueUrl`` action. ``GetQueueUrl``
        requires only the ``QueueName`` parameter. be aware of existing queue
        names:
        -  If you provide the name of an existing queue along with the exact
           names and values of all the queue's attributes, ``CreateQueue``
           returns the queue URL for the existing queue.
        -  If the queue name, attribute names, or attribute values don't match
           an existing queue, ``CreateQueue`` returns an error.
        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``
        Cross-account permissions don't apply to this action. For more
        information, see `Grant cross-account permissions to a role and a user
        name <https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name>`__
        in the *Amazon SQS Developer Guide*.
        :param queue_name: The name of the new queue.
        :param attributes: A map of attributes with their corresponding values.
        :param tags: Add cost allocation tags to the specified Amazon SQS queue.
        :returns: CreateQueueResult
        :raises QueueDeletedRecently:
        :raises QueueNameExists:
        """
        raise NotImplementedError
    @handler("DeleteMessage")
    def delete_message(