AWS::IAM::User doesn't take the 3 automatic stack tags

## Scope of request
Cloudformation doesn't add its default 3 tags to IAM users (stack-name, stack-id and logical-id)

## Expected behavior
The 3 CloudFormation automatic stack tags should be present on all resources

## Additional context
This is even more important because IAM users are global. If a stack is deployed regionally always adding the same name but not defining a name, it results on CloudFormation deploying the same name with random names on each of the 3 regions. The tag would allow to identify which stack on which region created it. Without it only by visiting each of the regions to match the random name.

## Helpful Links to speed up research and evaluation
Similar to #277, IAM Users also are not populated with the 3 automatically created tags.

## Category
Security (IAM)
Tagging

## Any additional context (optional)
Per [CloudFormation Resource Tag Documentation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-resource-tags.html), "All stack-level tags, including automatically created tags, are propagated to resources that AWS CloudFormation supports." This bug has lead to management issues in correlating IAM resources back to the owning stack.

No repository file, test, or entry point is identified. Start by reading the CloudFormation Resource Tag documentation and comparing this issue with #277; confirm whether AWS::IAM::User supports automatic stack tags. Done means stack-name, stack-id, and logical-id tags are propagated to IAM users, including regionally deployed stacks.

Written by the indexing model from the issue text.