### 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
Language <https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-creating-custom-policies.html>`__
           in the *Amazon SQS Developer Guide*.
        -  An Amazon SQS policy can have a maximum of 7 actions.
        -  To remove the ability to change queue permissions, you must deny
           permission to the ``AddPermission``, ``RemovePermission``, and
           ``SetQueueAttributes`` actions in your IAM policy.
        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_url: The URL of the Amazon SQS queue to which permissions are added.
        :param label: The unique identification of the permission you're setting (for example,
        ``AliceSendMessage``).
        :param aws_account_ids: The account numbers of the
        `principals <https://docs.
        :param actions: The action the client wants to allow for the specified principal.
        :raises OverLimit:
        """
        raise NotImplementedError
    @handler("ChangeMessageVisibility")
    def change_message_visibility(
        self,
        context: RequestContext,
        queue_url: String,
        receipt_handle: String,