Filterable Health Tags

[ceyonur]

Why this should be merged

• Adds filterable string tags to health workers
• Registers chain-related health checks with subnetIDs tags
• Adds a global tag for those checks like db/network. Global health checks are always returned regardless of filters.
• Adds tags optional param to Post request. Ex:

curl --location --request POST 'http://localhost:9660/ext/health' \
--header 'Content-Type: application/json' \
--data-raw '{
    "jsonrpc":"2.0",
    "id"     :1,
    "method" :"health.health",
    "params" :{
    "tags": ["29uVeLPJB1eQJkzRemU8g8wZDw5uJRqpab5U2mX9euieVwiEbL"]
    }

}'

• Adds tag optional query param. Supports multiple tag params. Ex:

curl --location --request GET 'http://localhost:9660/ext/health?tag=29uVeLPJB1eQJkzRemU8g8wZDw5uJRqpab5U2mX9euieVwiEbL' \
--header 'Content-Type: application/json' \
--data-raw '{
    "jsonrpc":"2.0",
    "id"     :1,
    "method" :"health.health",
}'

Closes: #1264

How this works

expands the Health result/register interface by adding input of optional tags to Register and Result methods.
Tracks tags > names map in the worker

How this was tested

Added unit tests

[StephenButtolph]

Just small stuff

[StephenButtolph]

Kinda weird that the key is subnetID and it returns subnetIDs... But I do think this is the best way to do this with the query params...

[ceyonur]

yea and it's even weirder that r.URL.Query().Get("subnetID") returns the first value for the key... alternatively we can use plural subnetIDs (now tags) and split string value by comas. but I probably would prefer singular key names (i.e tag over tags).

[danlaine]

just a few more nits. Once these are done LGTM

[danlaine]

1 final nit otherwise LGTM