### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current Behavior

I'm configuring the S3 bucket to have a lifecycle, everything works fine, but when I get the object, the header `Expiration` is not showing

### Expected Behavior

According to the documentation, if the bucket have a `lifecycle configuration` enabled, the header `expiration` should appear in the response

Executing the command
```bash
$ awslocal s3api get-object help
```

We get the documentation of `get-object` command and in the `OUTPUT` section we have:
>Expiration -> (string)
>          If the object expiration is configured (see PUT  Bucket  lifecycle),
>          the  response  includes this header. It includes the expiry-date and
>          rule-id key-value pairs providing object expiration information. The
>          value of the rule-id is URL-encoded.

### How are you starting LocalStack?

With a docker-compose file

### Steps To Reproduce

#### Created the bucket-lifecycle.json
```json
{
  "Rules": [
    {
      "ID": "My Rule ID",
      "Status": "Enabled",
      "Expiration": {
        "Days": 1
      },
      "NoncurrentVersionExpiration": {
        "NoncurrentDays": 1
      }
    }
  ]
}
```

####  Command for create the lifecycle configuration on a existing bucket
```bash
$ awslocal s3api put-bucket-lifecycle-configuration --bucket my-bucket --lifecycle-configuration file://bucket-lifecycle.json
```

#### Validate the configuration
```bash
$ awslocal s3api get-bucket-lifecycle-configuration --bucket my-bucket

output:
{
    "Rules": [
        {
            "Expiration": {
                "Days": 1
            },
            "ID": "My Rule ID",
            "Status": "Enabled",
            "NoncurrentVersionExpiration": {
                "NoncurrentDays": 1
            }
        }
    ]
}
```

#### Uploaded an object:
```bash
$ awslocal s3api put-object --bucket my-bucket --key teste.json --body bucket-lifecycle.json  --content-type application/json

output:
{
    "ETag": "\"eb702ecb4e41b09ca62934217d5f13af\""
}
```

#### Fetch the object
```bash
$ awslocal s3api get-object --bucket my-bucket --key teste.json bucket-lifecycle.json 

output:
{
    "AcceptRanges": "bytes",
    "LastModified": "2022-08-11T13:39:11+00:00",
    "ContentLength": 287,
    "ETag": "\"eb702ecb4e41b09ca62934217d5f13af\"",
    "VersionId": "null",
    "ContentLanguage": "en-US",
    "ContentType": "application/json",
    "Metadata": {}
}
```

### Environment

```markdown
- OS: MacOS Monterey
- LocalStack: 1.0.3
```


### Anything else?

_No response_
endpoint_url=_endpoint_url(),
        )
        url = presigned_client.generate_presigned_url(
            "get_", Params={"Bucket": s3_bucket, "Key": _key}, ExpiresIn=5
        )
        parsed = urlparse(url)
        query_params = parse_qs(parsed.query)
        # sig v2
        if "Signature" in query_params:
            query_params.pop("Expires", None)
        else:  # sig v4
            query_params.pop("X-Amz-Date", None)
        new_query_params = urlencode(
            {k: v[0] for k, v in query_params.items()}, quote_via=quote, safe=" "
        )
        invalid_url = urlunsplit(
            SplitResult(  # noqa
                parsed.scheme, parsed.netloc, parsed.path, new_query_params, parsed.fragment
            )
        )
        resp = .get(invalid_url, verify=False)
        assert resp.status_code in [
            400,
            403,
        ]  # the 
        exception = xmltodict.parse(resp.content)
        exception["StatusCode"] = resp.status_code
        snapshot.match("missing-param-exception", exception)
    @pytest.mark.aws_validated
    def test_s3_get_response_content_type_same_as_upload_and_range(self, s3_bucket, aws_client):