[Feature Request]: chroma browse fails with "Failed to load records" when using v2 API on local server

### Describe the problem

Environment:
Chroma version: 1.4.4
CLI version: 1.4.4
Steps to reproduce:
Start a local Chroma server at localhost:8000
Run chroma browse --local
Observe: (Error) Failed to load records
Expected behavior: chroma browse should successfully load and display records from the collection using the v2 API (/api/v2/...).
Actual behavior: The CLI fails to load records. Direct v2 API calls via curl work correctly:
curl http://localhost:8000/api/v2/tenants/default_tenant/databases/default_database/collections//get

Additional context: The v2 API endpoints work correctly via curl, suggesting the CLI is not using the correct API version or endpoint format.

### Describe the proposed solution

Update the chroma browse CLI command to use the v2 API endpoints (/api/v2/...) when communicating with a local Chroma server. Specifically:

- Replace any v1 API calls with the equivalent v2 endpoints, e.g.: /api/v2/tenants/{tenant}/databases/{database}/collections/{id}/get
- Default to default_tenant and default_database when no tenant/database flags are provided
- Optionally, add --tenant and --database flags to allow users to specify custom values

### Alternatives considered

_No response_

### Importance

nice to have

### Additional Information

_No response_

Start by locating the chroma browse CLI command and tracing how its --local mode builds requests to the Chroma server. Compare those requests with the documented /api/v2/tenants/{tenant}/databases/{database}/collections/{id}/get endpoint, then run the command against a local server and verify that records load; check custom tenant and database handling if flags are added.

Written by the indexing model from the issue text.