[FlyteCTL Feature] Add verbose logging for other components while using `--verbose`

[DarthBenro008]

Describe the feature/command for FlyteCTL

As discussed in https://github.com/flyteorg/flytectl/pull/359#pullrequestreview-1132613482 of https://github.com/flyteorg/flytectl/pull/359

The --verbose flag of flytectl sandbox start/teardown and flytectl demo start/teardown only captures logs of helm/k8s commands, we would want to capture the logs of other components as well like docker, k3s, etc. The above mentioned PR already brings support to interfacing with docker

I would be happy to send a PR for the same! :D

Provide a possible output or UX example

Kindly refer to https://github.com/flyteorg/flytectl/pull/359 for more details (screenshots attached)

Are you sure this issue hasn't been raised already?

• [X] Yes

Have you read the Code of Conduct?

• [X] Yes

[welcome[bot]]

Thank you for opening your first issue here! 🛠

[samhita-alla]

@DarthBenro008, if you could work on this issue as well, that'd be awesome!

[DarthBenro008]

I'd be happy to send a PR, can you kindly assign the issue to me?

[github-actions[bot]]

Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏

[github-actions[bot]]

Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏

[github-actions[bot]]

Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable. Thank you for your contribution and understanding! 🙏