[Bug] URI range validation is inconsistently applied to different target discovery mechanisms

[andrewazores]

Current Behavior

See #323 (#323 (comment))
See #444

cryostat/src/main/java/io/cryostat/discovery/Discovery.java

Line 204 in 446f0d7

// TODO apply URI range validation to the remote address

cryostat/src/main/java/io/cryostat/discovery/Discovery.java

Line 314 in 446f0d7

if (b.target != null) {

URI range validation should also be applied at the locations above, so that not only Custom Targets are validated to be within the expected range, but also that Discovery Plugins are within range and any targets published by Discovery Plugins are within range.

It may make sense to do this validation in the pre-persist hooks, ex.

cryostat/src/main/java/io/cryostat/targets/Target.java

Line 343 in 446f0d7

void prePersist(Target target) {

Expected Behavior

No response

Steps To Reproduce

No response

Environment

No response

Anything else?

No response

[andrewazores]

@Josh-Matsuoka want to take a stab at this?