Update docs contributing code block

[lzdanski]

Description

Added more detail for virtual environment set up to run docs locally. This can help technical writers who might have more experience working with Sphinx in a different project with a different implementation.

Related Issue(s)

N/A

Breaking Change?

None expected.

Checklist

• I have made corresponding changes to the documentation (if required)
• I have added tests that prove my fix is effective or that my feature works

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.96%. Comparing base (436fe98) to head (9de80ce).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2397   +/-   ##
=======================================
  Coverage   97.96%   97.96%           
=======================================
  Files         102      102           
  Lines        7013     7013           
=======================================
  Hits         6870     6870           
  Misses        143      143           

☔ 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.

[tatiana]

@lzdanski Since we’re using Hatch, which already manages its own virtual environments, requiring contributors to create another virtualenv step may be unnecessary. It could introduce redundancy or confusion, as hatch handles environment isolation for us. Perhaps we can simplify the instructions by relying on Hatch’s built-in environment management rather than a new docs_env, and let users install Hatch however they prefer. I'd vote for us not to make the changes proposed in this PR.

[lzdanski]

Based on the reviews, I've made the following changes:

1. @tatiana - Thinking ahead to encouraging docs contributions, a deterrent to submitting docs updates can be the complexity of setting up the full local development environment, compared to how straightforward the local docs builds can be. I've split the docs contributing into two scenarios: 1. If someone already has their local Cosmos development environment set up, they can just run hatch. 2. If someone only wants to work on docs, and doesn't have anything set up, which includes creating the docs_venv.

2. Added the recommended changes from @pankajkoti + @yetudada.

[tatiana]

@lzdanski, I gave some last feedback. It would be great if you could address it so we can merge this today.

[tatiana]

Thanks, @lzdanski , this will help future docs contributions!