[BUG] Correctly check arguments for chroma cli for chroma update

[priyankc]

Description of changes

When a user runs chroma update from the command line, the code should detect this command and run the update() function to check for newer versions of Chroma. It is incorrectly checking for the command line arguments

Test plan

pip install -e .

python3 -c "import sys; from chromadb.cli import cli; sys.argv = ['chroma', 'update']; cli.app()"

• Doesn't trigger chroma update. You will see a wrong message:

• Run the above with fix, you will see update run correctly.

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Fixes #4474

[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]

This PR corrects the logic used to detect the 'chroma update' command in the CLI, ensuring that the update() function is triggered when users invoke 'chroma update' from the command line. The previous implementation failed to recognize the command due to improper argument checking, which is now fixed by explicitly checking the first two sys.argv values.

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

[priyankc]

@itaismith I mistakenly created the PR against my fork.

This is the right PR.

[priyankc]

@itaismith Looks like the CI failures are not relevant to this PR. Is there anything else blocking this PR landing?