refactor use builder classes for collection request builders (issue #3272)

[Sukuna0007Abhi]

This PR refactors collection request builders to use classes that enforce a consistent build(session, logger, enabled_phase_names, days_until_collect_again) signature, fixing issue #3272.

changed

• Added CollectionRequestBuilder (abstract base class) that defines build(...).
• Implemented concrete builders: PrimaryCollectionRequestBuilder, SecondaryCollectionRequestBuilder, FacadeCollectionRequestBuilder, MLCollectionRequestBuilder.
• Added backward-compatible wrapper functions:
• build_primary_repo_collect_request(...)
• build_secondary_repo_collect_request(...)
• build_facade_repo_collect_request(...)
• build_ml_repo_collect_request(...)
• Added tests: test_collection_builders.py to assert subclassing, build presence, correct signatures and wrapper parity.

Why

• Ensures all collection request builders follow a consistent and enforceable API that accepts enabled_phase_names (as discussed in Use Classes to enforce consistent APIs #3272).
• Keeps existing call sites working via thin wrappers — no runtime behavior changed.

Ready for review ...

Fixes #3272

[MoralCode]

hmmm, maybe i wasnt expecially detailed in my underlying issue, or the fact that I said "classes" (plural) may have confused things.

@ABrain7710 is currently working on some improvements to task scheduling that will probably change these functions in a major way anyway, so I think that may give a better opportunity for refactoring this