This task focuses on ensuring that all OpenStack resources automatically created by Hypershift for Hosted Control Planes are tagged with a unique identifier, such as the HostedCluster ID. These resources include, but are not limited to, servers, ports, and security groups. Proper tagging will enable administrators to clearly identify and manage resources associated with specific OpenShift clusters.

Acceptance Criteria:

1. Tagging Mechanism: All OpenStack resources created by Hypershift (e.g., servers, ports, security groups) should be tagged with the relevant Cluster ID or other unique identifiers.
2. Automated Tagging: The tagging should occur automatically when resources are provisioned by Hypershift.
3. Consistency: Tags should follow a standardized naming convention for easy identification (e.g., cluster-id: <ClusterID>).
4. Compatibility: Ensure the solution is compatible with the current Hypershift setup for OpenShift Hosted Control Planes, without disrupting functionality.
5. Testing: Create automated tests or manual test procedures to verify that the resources are properly tagged when created.
6. Documentation: Update relevant documentation to inform administrators about the new tagging system, how to filter resources by tags, and any related configurations.