feat: adding a way to use different values for max capacity query

[maugustosemperfi]

✨ What kind of change does this PR introduce? (Bug fix, feature, docs update...)

Feature - Adds a new configurable maxCapacityAgeFilterDuration parameter to customize the age threshold for cache object cleanup.

⤵️ What is the current behavior?

When cleaning up cache objects over capacity, the getObjectsOverCapacity method uses a hardcoded Duration(days: 1) filter. This means only objects that haven't been touched in the last 24 hours are considered for removal, with no way to customize this behavior.

🆕 What is the new behavior (if this is a feature change)?

• Added maxCapacityAgeFilterDuration optional parameter to Config
• The getObjectsOverCapacity method now accepts a maxAge parameter
• CacheStore uses the configured duration (falling back to 1 day if not set)
• All repository implementations (CacheObjectProvider, JsonCacheInfoRepository, NonStoringObjectProvider) updated to support the new parameter

This allows users to configure how recently an object must have been accessed before it becomes a candidate for removal during over-capacity cleanup.

💥 Does this PR introduce a breaking change?

No - The parameter is optional with a default value matching the previous hardcoded behavior (Duration(days: 1)).

🐛 Recommendations for testing

1. Create a cache manager with custom maxCapacityAgeFilterDuration (e.g., Duration(seconds: 10))
2. Add objects exceeding capacity
3. Verify only objects older than the configured duration are cleaned up
4. Verify default behavior (no parameter) still uses 1 day threshold

📝 Links to relevant issues/docs

N/A

🤔 Checklist before submitting

• All projects build
• Follows style guide lines (code style guide)
• Relevant documentation was updated
• Rebased onto current develop

[Syed-Bipul-Rahman]

Thanks for adding the feature for max capacity query

[rickdijk]

main has moved since you opened this, and our changes to cache_object_provider.dart and test/mock.mocks.dart left it conflicting. I have merged main into your branch, resolved those conflicts and regenerated mock.mocks.dart with build_runner. Your change itself is untouched, apart from dart format reflowing your new lines to match the formatting pass on main. Once CI runs, flutter analyze will report that Config in lib/src/config/_config_io.dart and lib/src/config/_config_web.dart does not implement the new maxCapacityAgeFilterDuration getter. That was already the case before the merge, and adding it to both is what is left.