Add an option to rollback if there are tagging errors on the AWS::IAM::Role resource

### Name of the resource

AWS::IAM::Role

### Resource name

_No response_

### Description

Currently if CloudFormation cannot tag the AWS::IAM::Role. CloudFormation gives the below error within the Stack Events but proceeds with the deployment.

"Encountered a permissions error applying tags, please add required tag permissions. Retrying request without including tags. Details: Resource handler returned message: User: arn:aws:sts::123456789:example-assumed-role is not authorized to perform: < eg API: :iam:TagRole> on resource: arn:aws:iam::123456789:role/abc with an explicit deny in an identity-based policy."

The request is to add an option for the stack to fail and rollback, i.e a 'strict' mode. This is because for example when deploying using stack sets, it can be nearly impossible to detect this.

### Other Details

_No response_

Start with the AWS::IAM::Role resource and the described CloudFormation stack event for failed tagging permissions. Trace how stack deployment currently retries without tags and where a stack-level option could control that behavior. Done means strict mode causes the stack to fail and roll back instead of proceeding when tagging fails.

Written by the indexing model from the issue text.