CloudFormation stack update reports "Internal Failure" for AWS::Batch::JobQueue resource when only Tags property is updated

### Name of the resource

AWS::Batch::JobQueue

### Resource Name

_No response_

### Issue Description

When a changeset is created and then executed after updating Tags property for AWS::Batch::JobQueue resource, CloudFormation update fails with "Internal Failure" error. This is applicable to both console and 'cloudformation deploy' command.

### Expected Behavior

All tags changes should get applied to AWS::Batch::JobQueue resource.

### Observed Behavior

Stack update fails with "Internal Failure" error when a changeset is created and then executed with change in Tags property for AWS::Batch::JobQueue resource.

- However If the stack is updated directly, then the stack update goes through successfully. This is applicable to updating the stack using console and using update-stack API call.
- Also, new stack with updated Tags property will also deploy successfully.

### Test Cases

- Create a CF stack with AWS::Batch::JobQueue and some other resources
- Create a changeset with a change in Tags property value.
- Execute the changeset, update will fail for AWS::Batch::JobQueue resource with "Internal Failure" error.

### Other Details

_No response_

Start by reproducing the failure with an AWS::Batch::JobQueue, a tag-only change, and a CloudFormation changeset executed through the console or `cloudformation deploy`; compare it with direct `update-stack` behavior. Done means changeset execution applies all tag changes without the "Internal Failure" error.

Written by the indexing model from the issue text.