Bugfix/#18545 check druid default rules

[ljblancoredborder]

Checking druid coordinator has default rules and they are not loading forever
We want to limit druid duration of all datasources by default to not take everything, just to make druid not to keep infinite data and getting stucked

The test included try to get the rules from the service. The curl won't fail. However, it's stdout can be empty depending on the situation:
If we are testing against the host of the service (ie. 10.0.209.22) the response will be an array of rules and one load rule can't be "forever"
if we are testing against another node (ie. 10.0.209.20) the response will be empty. (AND THE REST OF THE TEST IS SKIPPED)
For now we are accepting both as correct tests. So the question is:
Do all nodes in a cluster behave the same and the tests should be improved to not skipping in any case?

[the-label-bot]

The Label Bot has predicted the following:

Category	Value	Confidence	Applied Label

[manegron]

La cierro porque lo de las reglas es algo opcional y no deberíamos forzarlo a nivel de test.