239 update developer setup documentation

[blakedehaas]

Checklist

(Need feedback on how/if to handle these two)

• The changelog.md has been updated if necessary
• Dependency spec updated if necessary

Summary

Updated Developer Documentation to remove docker-compose references and add missing commands

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.82%. Comparing base (9a65ffb) to head (3e462cf).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #240   +/-   ##
=======================================
  Coverage   94.82%   94.82%           
=======================================
  Files          48       48           
  Lines        3868     3868           
=======================================
  Hits         3668     3668           
  Misses        200      200           

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

[medley56]

I think we need to make a distinction in these docs that these steps are only required if a user is not using the devcontainer. If they are in the devcontainer, all of this setup should already be taken care of.

[medley56]

I'm pretty sure Github won't let you use HTTPS any more so this is a basic standard requirement, not a recommendation by us.

[medley56]

This is very environment dependent. In the devcontainer, this should be taken care of. Outside the devcontainer, it's the wild west and I don't think we can provide a suggestion to users. They just need to know their development environment. For example, I don't even have an env file in this location.

[medley56]

This is up to user IDE configuration and how they want to use the virtual environment. Most IDEs will default to automatically activating the venv for new terminal sessions but users can manage that however they want to.