Updates to collection sampling methods

[mihow]

Summary

• Fixes Fix error when populating collections #716
• Adds support for filtering by a date range
• Remove default max_num of 100 which was a hidden default
• Shuffle collection if a max_num is provided

Screenshots

If applicable, add screenshots to help explain this PR (ex. Before and after for UI changes).

Checklist

• I have tested these changes appropriately.
• I have added and/or modified relevant tests.
• I updated relevant documentation or comments.
• I have verified that this PR follows the project's coding standards.
• Any dependent changes have already been merged to main.

[sentry-io]

🔍 Existing Issues For Review

Your pull request is modifying functions with the following pre-existing issues:

📄 File: ami/main/models.py

Function	Unhandled Issue
sample_captures_by_interval	ValueError: Queryset must be provided, and it should be limited to a Project. ... Event Count: 6

---

_{Did you find this useful? React with a 👍 or 👎}

[netlify]

✅ Deploy Preview for ami-dev ready!

Name	Link
🔨 Latest commit	4e0aa2d
🔍 Latest deploy log	https://app.netlify.com/sites/ami-dev/deploys/67a442d3174ebf0008ad64a2
😎 Deploy Preview	https://deploy-preview-717--ami-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 72 Accessibility: 89 Best Practices: 92 SEO: 100 PWA: 80 View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[mihow]

@annavik I had to fix a couple things for the labeling project to create their collections. I added a date field to the collections form in the simplest way possible. But I bet we can add a real date picker from the Nova components?? Also a checkbox for "shuffle", and make the sampling method a hidden field. I'll add a ticket for that unless you beat me to it.