feat: Add ownership parameter to storage collection listing methods

[nmanerikar]

Description

Adds an ownership query parameter (ownedByMe | sharedWithMe) to the list() method on DatasetCollectionClient, KeyValueStoreCollectionClient, and RequestQueueCollectionClient (both sync and async variants). This allows filtering listed storages by whether they are owned by the user or shared with the user.

Testing

Includes unit tests verifying the parameter is correctly passed through to the API request for all three storage types.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.84%. Comparing base (2f67a5d) to head (3328587).
⚠️ Report is 3 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #696      +/-   ##
==========================================
+ Coverage   94.79%   94.84%   +0.04%     
==========================================
  Files          45       45              
  Lines        4403     4405       +2     
==========================================
+ Hits         4174     4178       +4     
+ Misses        229      227       -2     

Flag	Coverage Δ
integration	94.84% <100.00%> (+0.04%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[tobice]

Thanks Nish!

From my PoV, it's just piping the param to API, which makes sense. I'll leave the Python stuff to the tooling team.

[vdusek]

Looks good, just one small thing:

Could you please move the definition of the ownership type

Literal['ownedByMe', 'sharedWithMe']

to a _types.py and give it a name?

This is the preferred approach for now. In the future, it should be derived from the specs and live in _models.py, but _types.py is currently the right place for manually defined types.

Thanks.

[vdusek]

LGTM, thanks

[vdusek]

I was wondering whether we should have a conversion mechanism between snake_case and camelCase for literal values. But we already have camelCase values in the codebase, e.g.:

sort_by: Literal['createdAt', 'stats.lastRunStartedAt'] | None = 'createdAt'

So let's merge this as-is.

However, we should consider whether to introduce such a mechanism before v3 - allowing snake_case values in the Python interface and converting them to camelCase for the API under the hood.

cc @janbuchar , @Pijukatel