Summary:
Investigate options to remove the disagg “failure expected” build variants from the develop Evergreen waterfall to a different waterfall page (created via a feature branch).

Problem:
The disagg variants intentionally fail and currently appear red on the develop waterfall. This:

• Impacts the “develop should be green” health signal
• Adds noise/overhead for barons

At the same time, keeping them on develop enables:

• BB-UI triaging without extra setup
• Commit level testing

We need to determine whether Evergreen tooling supports a cleaner solution (e.g., separate Evergreen project and auto-rebasing with develop) without introducing high maintenance overhead (e.g., constant rebasing, branch management complexity).

Goals (1 day Spike):

• Validate whether disagg variants can run on a different evergreen project.
• Confirm whether BB-UI triaging works (seperately) with a separate Evergreen project.
• Estimate ongoing maintenance cost (do we need constant rebasing with develop?).

Non-Goals:

• Full implementation (unless trivial).

If the implementation is unnecessarily complicated, we should drop the task for now.