docs: add instructions for stopping Flyte sandbox

[muskan-creates352]

Tracking issue

Why are the changes needed?

->While exploring the sandbox deployment documentation, I noticed that the command to stop the Flyte sandbox was not mentioned. This can be helpful for users who want to stop the local sandbox after testing.

What changes were proposed in this pull request?

->This PR adds a small section in sandbox.rst explaining how to stop the Flyte sandbox using the command:
flytect1 demo stop
This will help users working with the local Flyte sandbox environment.

How was this patch tested?

->The documentation change was verified by reviewing the updated section in sandbox.rst.

Labels

Please add one or more of the following labels to categorize your PR:

• added: For new features.
• changed: For changes in existing functionality.
• deprecated: For soon-to-be-removed features.
• removed: For features being removed.
• fixed: For any bug fixed.
• security: In case of vulnerabilities

This is important to improve the readability of release notes.

Setup process

Screenshots

Check all the applicable boxes

• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.

Related PRs

Docs link

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.97%. Comparing base (cd7371f) to head (ab011b0).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #7029   +/-   ##
=======================================
  Coverage   56.96%   56.97%           
=======================================
  Files         931      931           
  Lines       58276    58276           
=======================================
+ Hits        33198    33201    +3     
+ Misses      22019    22016    -3     
  Partials     3059     3059           

Flag	Coverage Δ
unittests-datacatalog	53.51% <ø> (ø)
unittests-flyteadmin	53.15% <ø> (ø)
unittests-flytecopilot	43.06% <ø> (ø)
unittests-flytectl	64.14% <ø> (+0.04%)	⬆️
unittests-flyteidl	75.71% <ø> (ø)
unittests-flyteplugins	60.19% <ø> (ø)
unittests-flytepropeller	53.71% <ø> (ø)
unittests-flytestdlib	62.62% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[muskan-creates352]

Hi sir, I have fixed the DCO issue and updated the commit. Please let me know if any further changes are needed. Thank you!

[muskan-creates352]

Hi,
I’ve updated the PR and resolved the DCO issue, and all checks are now passing.

Whenever you have some time, I would be grateful if you could kindly review it. Please let me know if any changes are needed from my side.

Thank you so much for your time and guidance!

[davidmirror-ops]

Hi, thanks for contributing. Please fix the DCO test

[Sovietaced]

It seems like a bunch of unintentional changes made it into here. @muskan-creates352 can you clean that up as well as the DCO?

[muskan-creates352]

Hi, thanks for your feedback!

I've cleaned up the PR and ensured that only the intended documentation change is included. I've also fixed the DCO issue.

Please let me know if any further changes are needed.

[muskan-creates352]

Hi, the PR has been cleaned up and rebased on the latest upstream. All checks have passed. Could you please review when you get a chance? Thanks!

[muskan-creates352]

Hi, I have updated the branch with the latest changes from the base branch.

All checks are passing on my side. Could you please review it when you get a chance?

Thanks a lot!