[Task] Metadata and JVM ID computation can block threads

[andrewazores]

For example, try simply defining a custom target like fake:9091, where fake is not a resolvable hostname. This should succeed very quickly because all that needs to be done is inserting a small update to the discovery database. However, this also triggers a target discovery event internally and notifies the metadata manager of the change, which then uses the notifying thread (in this case, an HTTP webserver thread that is processing the custom target request) to perform some work around checking if metadata is fresh, which also requires connecting to that new target definition to compute its hash ID and check the list of active recordings.