[ENH] CLI - Set Chroma env variables

[itaismith]

Description of changes

Adding chroma db connect --env-file which sets environment variables required for connecting to ChromaCloud in the .env file in the current directory (or create it). The chroma db connect --env-vars option will output to the terminal.

Test plan

Manual testing.

Documentation Changes

Included in this PR under CLI docs.

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[propel-code-bot]

Enhance CLI: Add Chroma Environment Variable Commands to db connect

This PR introduces two new options to the chroma db connect CLI command: --env-file and --env-vars. The --env-file flag writes Chroma environment variables (API key, tenant, database) into a .env file in the current directory, creating or updating it as needed without duplicating keys. The --env-vars flag outputs the required environment variables directly to the terminal. Both options are mutually exclusive with language-based code snippet generation, and documentation has been updated to reflect this new functionality.

Key Changes:
• Added --env-file and --env-vars flags for chroma db connect in CLI
• Implementation to write or update a .env file with Chroma environment variables, avoiding duplicate keys
• Ability to print Chroma environment variables to terminal via --env-vars
• Expanded CLI argument parsing to handle flag exclusivity and usage errors
• Updated and expanded CLI documentation for these new options
• Introduced constants for environment variable names to avoid hardcoding

Affected Areas:
• rust/cli/src/commands/db.rs
• rust/cli/src/utils.rs
• docs/docs.trychroma.com/markdoc/content/cli/commands/db.md

This summary was automatically generated by @propel-code-bot