This is a request for Pinpoint to allow passing different "extra test arguments" for the HEAD and HEAD+patch runs of a perf try job.

Ideally the patch itself would also be optional, so that we can start a job that just compares HEAD[default args] to HEAD[custom args].

This would make it easier to investigate the performance impact of new Chrome features that are landed behind an --enable-features=Foo flag or similar.