Remove `topology` configmap on kuadrant operator uninstall

Link the lifecycle of the kuadrant operator with the `topology` configmap. Currently, when the operator starts, it will create and maintain the `topology` configmap in the namespace where the operator is deployed. It is missing the implementation of the removal of the `topology` configmap when the operator is deleted.

> Note: The ConsolePlugin resource, together with the associated deployment and service, follows the life events of the `topology` configmap. When the topology is created, so it is the ConsolePlugin (on openshift). Whereas when the topology is deleted, so it is the ConsolePlugin and associated resources. The ConsolePlugin was introduced in https://github.com/Kuadrant/kuadrant-operator/pull/884

Start by tracing where the Kuadrant operator creates and maintains the topology ConfigMap, then inspect the lifecycle handling for the ConsolePlugin and its associated deployment and service. Implement the missing deletion path so removing the operator also removes the topology and dependent resources, and verify that creation and deletion remain linked.

Written by the indexing model from the issue text.