Feature Request: Allow separate tags for each Scheduling Queues, HeadNode, and all parallelcluster managed storage (fsx, efs, ebs, etc)

For accounting purposes, and specifically linking to [cost allocation tags](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/custom-tags.html) within AWS. I would like to be able to uniquely tag all resources created by parallelcluster: scheduling queues, the Head Node, and all associated storage . Currently the [tags parameter](https://docs.aws.amazon.com/parallelcluster/latest/ug/Tags-v3.html) tags all resources with the same tag.

Start with the current Tags parameter described in the linked Tags-v3 documentation and map how it is applied to queues, the Head Node, and managed storage. Define separate tag inputs and verify that each resource class receives its intended cost-allocation tags; the issue provides no named files or tests, so repository discovery is required.

Written by the indexing model from the issue text.