Fix "quicksight" identify type, update cfn caller templates + clearer admin user/dashboard user creation

[georgepstaylor]

This PR makes some fixes discovered during a new deployment.

• Fixes using "QUICKSIGHT" as the identity type for a user by adding a try() to the conditional as terraform evaluates all sides before comparing.
• Updates the "AWS Billing Data Export Aggregation" cfn template to v0.2.0 to fix an issue with the remote stacks requiring new inputs.
• Changes the conditional logic for creating an admin user. The username and email need to be both provided as well as a flag enable_quicksight_admin in order for an admin user to be created (username/email configurable as before)
• var.quicksights_username renamed to var.quicksight_dashboard_owner to increase clarity around what this user/input is used for.

The default logic is now that the destination module will create an admin user 'admin' and that same user will be used as the dashboards owner. The local to evaluate whether an admin user should be created or not is removed so that a terraform error is raised when enable_quicksight_admin=true and var.quicksight_admin_email has not be set (due to email being a required attr for the aws_quicksight_user resource. You will be able to stop this module managing the admin user by setting enable_quicksight_admin=false

[github-actions]

Pull Request Review Status

• 🖌 Terraform Format and Style: success
• 🔍 Terraform Linting: success
• 👮 Terraform Security Check: success
• 👮 Terraform Security Checkov: success
• 🔘 Terraform Tests: success
• 🔧 Terraform Initialisation: success
• 🤖 Terraform Validation: success
• 🤖 Terraform Example Validation: success
• 📖 Terraform Documentation: success
• 🔖 Commitlint: success

Working Directory: examples/basic
Pusher: @georgepstaylor, Action: pull_request
Workflow Run Link: https://github.com/appvia/terraform-aws-cudos/actions/runs/13589260554

[gambol99]

LGTM .. thank you kindly 🫡