Add mechanism for cleaning up the Elastic stack

Many a times, we observe an issue where the elastic stack doesn't come up when we run elastic-package stack up -v.
It usually gets stuck at "Kibana not ready state".

Below are the Kibana logs when the stack is stuck at this point:

[2022-05-25T11:07:11.635+00:00][INFO ][savedobjects-service] [.kibana] INIT -> CREATE_NEW_TARGET. took: 19ms.
[2022-05-25T11:07:11.637+00:00][INFO ][savedobjects-service] [.kibana_task_manager] INIT -> CREATE_NEW_TARGET. took: 14ms.
[2022-05-25T11:07:12.408+00:00][INFO ][plugins.screenshotting.chromium] Browser executable: /usr/share/kibana/x-pack/plugins/screenshotting/chromium/headless_shell-linux_arm64/headless_shell
[2022-05-25T11:07:41.639+00:00][ERROR][savedobjects-service] [.kibana] Action failed with ‘Request timed out’. Retrying attempt 1 in 2 seconds.
[2022-05-25T11:07:41.640+00:00][INFO ][savedobjects-service] [.kibana] CREATE_NEW_TARGET -> CREATE_NEW_TARGET. took: 30004ms.

**As part of this issue, would like to record the steps one can follow to overcome this issue.**

Start with the elastic-package stack up -v command and the provided Kibana timeout logs. Investigate and verify the cleanup or recovery steps for a stack stuck at "Kibana not ready", then document them in the project's documentation. The work is done when a newcomer can follow the recorded steps to recover the Elastic stack.

Written by the indexing model from the issue text.