[Housekeeping] Enable verbose logging for sandbox and demo environments

[pmahindrakar-oss]

Describe the issue

Currently its hard to debug errors in sandbox and demo environments if the installation fails during helm installation .
Enable verbose logging for helm commands and also kubectl commands

https://kubernetes.io/docs/reference/kubectl/cheatsheet/#kubectl-output-verbosity-and-debugging

The default option should be with this flag off.

 flytectl demo start --verbose
 flytectl sandbox start --verbose

Have similar flags during teardown of the environments

flytectl demo teardown --verbose
flytectl sandbox teardown --verbose

What if we do not do this?

Longer debugging cycles

Related component(s)

flytectl,flyte

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

• Yes

Have you read the Code of Conduct?

• Yes

[yindia]

cc: @TheYk98

[GrayFlash]

Hey @pmahindrakar-oss @samhita-alla can I pick up this issue??

[samhita-alla]

@GrayFlash, will have to assign it to Hemanth as he created a PR already.

[GrayFlash]

oh no issues. @samhita-alla is there any decent feature related issue I can work on?? flytectl repo seems to have no such issues.

[samhita-alla]

@GrayFlash, have you seen #2777?

[GrayFlash]

Sure working on it @samhita-alla going through the codebase and docs properly.!!

[github-actions]

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]

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]

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! 🙏