[Bug] Cannot delete custom targets that no longer point to a JVM

[andrewazores]

Current Behavior

To replicate it create a custom target and use the service in the connection URL, the remove the port 9091 from the service
the pod restart when I try to open the recordings for the custom target
cannot delete custom target from topology view

I think this can be tested in the smoketest by running a target application with JDP turned off and without Podman discovery annotations, so that it is present but not discoverable by default. Then define a custom target pointing to it. Then podman stop the target application, and podman run to restart it but this time with a different JMX port (or none).

The first "pod restart" issue is probably #1778 .

The "cannot delete custom target" seems related but may be a different bug.

Expected Behavior

No response

Steps To Reproduce

No response

Environment

No response

Anything else?

No response