Turn off optimizely on build.

[angaither]

Yes, I really do mean it.
Fixes #5811

[sergiitk]

@angaither But this code is being executed on pull stage.
Did you intend it to?

[angaither]

@sergii-tkachenko yes, just so we can turn off it off locally #1507

[sergiitk]

@angaither Can you also drush pmu (pm-uninstall) it?

[angaither]

@sergii-tkachenko sure, but why would we also need to uninstall?

[sergiitk]

@angaither Because that's the correct way to turn modules off.
It will drop its schema and remove its variables. See optimizely_uninstall().

[sergiitk]

Also, not "on staging", locally. This is the line that confused me initially, I thought it's intended to be disabled on staging.

[angaither]

@sergii-tkachenko I don't think we need to uninstall it, it's just removing tables, all we want is the JS to not be executed locally

[sergiitk]

It will be more consistent to pass -y as the first argument: this is a core-global-option. Not all drush submodules accept global options passed passed as the first argument.

[sergiitk]

👍