[BUG] Having the first filter step be disabled and tied to the second step causes problems

[rogin]

I'm migrating popular requests from NextGen's repo. This was issue #4470

Describe the bug
If the first listed filter step is disabled and "AND"ed or "OR"ed with the second step, something bad happens (fails to deploy or bricks?). Multiple people have been bitten by this in their Prod environments.

To Reproduce

1. Open channel source filter
2. Disable the first step
3. Add a second step, enabled, with an AND to the first step
4. Save the channel and deploy it

Expected behavior
The channel deploys and the disabled step does not execute

Actual behavior
Problem occurs

Additional context
Discussion around this focused on either disabling saves with this faulty configuration, allowing the configuration but fixing the auto-generated code, or make whatever filter is the first enabled be the first filter and then and / or others that follow.