Feature/monitor peers flag

[cybertunnel]

During strategies.yaml creation, the file contains hosts which are &peer# if they are inside the same cache group. The health of peers is currently not provide value. So having the ability to turn off the monitoring of peers since no traffic should be going to them, helps reduce computation and memory utilization. This also slims down the logs from unnecessary chatter.

---

Which Traffic Control components are affected by this PR?

• Traffic Control Health Client (tc-health-client)

What is the best way to verify this PR?

This PR includes an updated copy of tc-health-client.json for testing. Additionally, the tmagent_test.go test has updated the TestReadStrategiesDotYaml with tests for testing from reading from the tc-health-client.json config file, but also a manual true and false value, with the proper expected results checked.

PR submission checklist

• This PR has tests
• This PR has documentation
• This PR has a CHANGELOG.md entry
• This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY

[cybertunnel]

NOTE: This Does require yamlv3 pkg to be installed. Both v2 and v3 can co-exist, but v3 is needed for the yaml.Node struct. Which is how this is able to parse the peers.

[codecov]

Codecov Report

Merging #7672 (579d49c) into master (75ec56f) will decrease coverage by 38.11%.
Report is 46 commits behind head on master.
The diff coverage is 6.09%.

@@              Coverage Diff              @@
##             master    #7672       +/-   ##
=============================================
- Coverage     65.05%   26.95%   -38.11%     
  Complexity       98       98               
=============================================
  Files           314      686      +372     
  Lines         12365    80539    +68174     
  Branches        907       90      -817     
=============================================
+ Hits           8044    21706    +13662     
- Misses         3968    56761    +52793     
- Partials        353     2072     +1719     

Flag	Coverage Δ
golib_unit	48.10% <0.00%> (?)
grove_unit	4.60% <ø> (?)
t3c_unit	4.95% <5.88%> (?)
traffic_monitor_unit	21.30% <0.00%> (?)
traffic_ops_integration	69.39% <90.62%> (-0.03%)	⬇️
traffic_ops_unit	22.29% <4.32%> (?)
traffic_portal_v2	?
traffic_stats_unit	10.14% <ø> (?)
unit_tests	23.64% <4.26%> (-50.14%)	⬇️
v3	57.79% <ø> (ø)
v4	79.18% <ø> (ø)
v5	78.52% <90.62%> (-0.12%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed	Coverage Δ
cache-config/t3c-apply/config/config.go	0.00% <0.00%> (ø)
cache-config/t3c-apply/t3c-apply.go	0.00% <0.00%> (ø)
lib/go-atscfg/parentdotconfig.go	65.76% <ø> (ø)
lib/go-tc/cdns.go	0.00% <ø> (ø)
lib/go-tc/deliveryservice_servers.go	0.00% <0.00%> (ø)
lib/go-tc/federation_resolver.go	45.45% <0.00%> (ø)
traffic_monitor/tmclient/tmclient.go	0.00% <0.00%> (ø)
...c_ops/traffic_ops_golang/cachegroup/cachegroups.go	14.93% <0.00%> (ø)
...raffic_ops/traffic_ops_golang/cdn_lock/cdn_lock.go	0.00% <0.00%> (ø)
...ops/traffic_ops_golang/deliveryservice/eligible.go	55.27% <0.00%> (ø)
... and 20 more

... and 568 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[jpappa200]

Looks good, works as intended.