PH: Add a longer running read-only trx for tests

[heifner]

• Create a logging-template.json for tests instead of using the example one in programs/nodeos since the configured gelf logging was wasting a thread and cpu when no gelf logging is being used in tests.
• Add a new doitslow action to payloadless contract for use in tests and performance harness runs.

Example of using the new longer running read-only trx in a performance run:
https://github.com/AntelopeIO/leap/actions/runs/6318554443

./tests/PerformanceHarnessScenarioRunner.py findMax testApiOpMode --max-tps-to-test 1000 overrideBasicTestConfig -v --http-threads 4 --api-nodes-read-only-threads 8 --read-only-write-window-time-us 1000 --read-only-read-window-time-us 450000 --account-name payloadless --abi-file payloadless.abi --wasm-file payloadless.wasm --contract-dir unittests/test-contracts/payloadless --user-trx-data-file tests/PerformanceHarness/readOnlySlowTrxData.json

      "TPS": {
        "min": 995,
        "max": 1004,
        "avg": 1000.0,
        "sigma": 0.8301741920760902,
        "emptyBlocks": 0,
        "numBlocks": 297,
        "configTps": 1000,
        "configTestDuration": 150,
        "tpsPerGenerator": [
          1000
        ],
        "generatorCount": 1
      },
      "TrxCPU": {
        "min": 5655.0,
        "max": 10308.0,
        "avg": 6548.978346666667,
        "sigma": 1362.3947007864986,
        "samples": 150000
      },

Which means 1000*6549=6,549,000us worth of trx execution within a 1,000,000us window.

[linh2931]

I like the example in the PR description, which shows the read-only threads are occupied most of the time.

[linh2931]

This is more clear.