Refactor Optimize

[amarvin]

Optimize finds optimal add/drop pairs sequentially, which is highly interpretable but suboptimal. It'd be better to allow all add/drops to find the optimal roster, then post-process to determine a priority list of add/drop pairs.

1. Optimize roster allowing any number of adds and drops
2. If more drops than adds, re-optimize to find who to drop first
3. For Max(adds, remaining drops), re-optimize to find a priority for add/drop pairs

Perhaps allowing waiver wire claims for adds should be an optional input to Optimize, to isolate that capability.

[amarvin]

For step 2, drop based on VOR (#36).