feat: add configuration for Monitor Pinger service

[Ivo-Yankov]

Description

• Adds dynamic configuration to the Pinger service.
• Requires feat: add Pinger config full-stack-testing#959 to be merged and a new release to be created

Related Issues

• Closes Setup mirror node monitor Pinger service #511

[github-actions]

E2E Mirror Node Tests Coverage Report

 1 files  ±0  1 suites  ±0   1m 38s ⏱️ - 2m 21s
12 tests ±0  6 ✅  - 6  5 💤 +5  1 ❌ +1 
13 runs  ±0  6 ✅  - 7  6 💤 +6  1 ❌ +1 

For more details on these failures, see this check.

Results for commit 0b4b793. ± Comparison against base commit fa3a316.

♻️ This comment has been updated with latest results.

[github-actions]

E2E Relay Tests Coverage Report

1 files  ±0  1 suites  ±0   2m 41s ⏱️ -1s
5 tests ±0  5 ✅ ±0  0 💤 ±0  0 ❌ ±0 
6 runs  ±0  6 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 0b4b793. ± Comparison against base commit fa3a316.

♻️ This comment has been updated with latest results.

[JeffreyDallas]

Maybe add a flag so user has an option to turn on or off pinger service,
my experience is there are many background transactions from pingers, sometimes had to check log when debugging other issues.

[github-actions]

Unit Test Results - Linux

  1 files  ±0   19 suites  ±0   46s ⏱️ ±0s
126 tests ±0  126 ✅ ±0  0 💤 ±0  0 ❌ ±0 
152 runs  ±0  152 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 0b4b793. ± Comparison against base commit fa3a316.

[github-actions]

Unit Test Results - Windows

  1 files  ±0   19 suites  ±0   1m 34s ⏱️ +3s
126 tests ±0  126 ✅ ±0  0 💤 ±0  0 ❌ ±0 
152 runs  ±0  152 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 0b4b793. ± Comparison against base commit fa3a316.

[github-actions]

E2E Node PEM Stop Tests Coverage Report

12 tests  ±0   12 ✅ ±0   2m 37s ⏱️ -1s
 1 suites ±0    0 💤 ±0 
 1 files   ±0    0 ❌ ±0 

Results for commit 0b4b793. ± Comparison against base commit fa3a316.

[github-actions]

E2E Node PFX Kill Tests Coverage Report

12 tests  ±0   12 ✅ ±0   2m 52s ⏱️ +2s
 1 suites ±0    0 💤 ±0 
 1 files   ±0    0 ❌ ±0 

Results for commit 0b4b793. ± Comparison against base commit fa3a316.

[github-actions]

E2E Tests Coverage Report

57 tests  ±0   57 ✅ ±0   3m 16s ⏱️ -51s
 9 suites ±0    0 💤 ±0 
 1 files   ±0    0 ❌ ±0 

Results for commit 0b4b793. ± Comparison against base commit fa3a316.

[github-actions]

E2E Node Local Build Tests Coverage Report

8 tests  ±0   8 ✅ ±0   2m 44s ⏱️ -2s
2 suites ±0   0 💤 ±0 
1 files   ±0   0 ❌ ±0 

Results for commit 0b4b793. ± Comparison against base commit fa3a316.

[github-actions]

E2E Node Add Tests Coverage Report

20 tests  ±0   16 ✅ ±0   11m 13s ⏱️ +11s
 2 suites ±0    3 💤 ±0 
 1 files   ±0    1 ❌ ±0 

For more details on these failures, see this check.

Results for commit 0b4b793. ± Comparison against base commit fa3a316.

[jeromy-cannon]

pick back up later