Setup mirror node monitor Pinger service

[Ivo-Yankov]

Feature to Enhance

Currently there is an issue in the network node that causes record files to only be exported when a new one is generated. This means that in networks with sparce transactions the latest one may become "stuck". This can be prevented with setting up a Pinger service in the Mirror node Monitor pod, which periodically creates small CRYPTO_TRANSFER transactions. After some quick testing I found that this can double the performance of the Solo network. There are also some test suites in the Smart Contracts repo that fail with a TIMEOUT errors, which should be resolved by this.

Requested Enhancement

Implement a similar solution to the one in the local node.

Business Need

The user experience when running end-to-end tests against a locally setup solo network is really poor due to the slow transaction processing.

Additional Context

No response