Add request start and end parameter to sleep runner

[VijayanB]

Description

Worker coordinator expects every runner to have request start and request end key.
Added client request start and client request end before and after sleep.

Issues Resolved

#485

Testing

• New functionality includes testing

[Describe how this change was tested]

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[saimedhi]

@VijayanB, Have you tested if this issue is resolved with this fix?

[VijayanB]

@VijayanB, Have you tested if this issue is resolved with this fix?

@saimedhi Yeah, it worked locally for my test procedure.

[VijayanB]

@gkamat @IanHoang Any update on this?

[IanHoang]

@saimedhi @VijayanB are there any other runners that require similar changes?

[IanHoang]

LGTM. If there are any other issues that require similar changes, we should create an issue to keep track of them and close them out.

[Kyle-sandeman-mrdfood]

Good day

I can open an Issue if this is not the right place to report a regression.
Side note: I am not familiar with this repo, but #450 seems to have a change related to this PR.

With a simple setup of OSB 1.6.0 and this added to my existing test_procedures->schedule:

{
  "operation": {"operation-type": "sleep", "duration": 1.5}
}

I am getting (after my other operations and after the sleep completes):

2024-06-18 14:22:26,790 ActorAddr-(T|:63310)/PID:58826 osbenchmark.worker_coordinator.worker_coordinator INFO Choosing [unthrottled] for [sleep].
2024-06-18 14:22:26,790 ActorAddr-(T|:63310)/PID:58826 osbenchmark.worker_coordinator.worker_coordinator INFO Creating iteration-count based schedule with [None] distribution for [sleep] with [0] warmup iterations and [1] iterations.
2024-06-18 14:22:26,790 ActorAddr-(T|:63310)/PID:58826 osbenchmark.worker_coordinator.worker_coordinator INFO iteration-count-based schedule will determine when the schedule for [sleep] terminates.
2024-06-18 14:22:28,292 ActorAddr-(T|:63310)/PID:58826 osbenchmark.worker_coordinator.worker_coordinator ERROR Could not execute schedule
Traceback (most recent call last):

  File "/Users/kylesandeman/.benchmark/venv/lib/python3.11/site-packages/osbenchmark/worker_coordinator/worker_coordinator.py", line 1592, in __call__
    request_start = request_context.request_start
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/Users/kylesandeman/.benchmark/venv/lib/python3.11/site-packages/osbenchmark/client.py", line 54, in request_start
    return self.ctx["request_start"]
           ~~~~~~~~^^^^^^^^^^^^^^^^^

KeyError: 'request_start'

Changing the Sleep Runner code to do the on_client_request_start first seems to fix it.
The code in #450 seems to require you to call this function first....

    async def __call__(self, opensearch, params):
        sleep_duration = mandatory(params, "duration", "sleep")
        try:
            request_context_holder.on_client_request_start()
            opensearch.on_request_start()
            await asyncio.sleep(sleep_duration)
        finally:
            opensearch.on_request_end()
            request_context_holder.on_client_request_end()