Check a demo for service collisions (browser session)

Reads one running demo of a stack profile on the organisation’s staging cluster and answers whether two services set up from a service package built on the profile could run side by side on one cluster. Every service gets a namespace of its own while each chart keeps its release name, so a cluster-scoped object the demo’s releases own (ClusterRole, ClusterRoleBinding, CustomResourceDefinition, admission webhook configurations, PriorityClass, StorageClass, IngressClass, Namespace) whose name does not carry the demo’s namespace (which its stack is named after) collides with a second service’s copy of it. Services and Secrets whose names do carry it are listed as instance-specific, since a package connection naming them would not match another service. Only names, Secret types and Helm’s release annotation are kept; the Secret data the listing carries is dropped, never kept or returned, and nothing is installed or written. verdict is no_collision only when every kind was read and nothing collides, collisions when something does, and unknown when the demo, or a kind, could not be read; reason says why.