Operator Subscription resources support users entering further config information about how the operator should be deployer or installed by OLM. These include Env/EnvFrom, Volumes, VolumeMounts, Tolerations and Resources, as seen in the OLM documentation for Subscription Config: https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/design/subscription-config.md Today that information can only be configured via YAML, however the console should support configuration of these as well when installing an operator.

For this story, specifically the configuration of Env/EnvFrom and Tolerations should be supported, as those are low-hanging-fruit since we already have console UI widgets to support editing those configs we can reuse. These could be surfaced under an 'advanced configuration' area on the Install Operator form, and also be surfaced in the operator details for reference as well.

Outdated UX design: https://docs.google.com/document/d/1Vv8JYPf6UPgOtHS5MQiEJrwijArHGWHnhP8tjC1mCl8/edit?usp=sharing 

UX design: https://github.com/openshift/openshift-origin-design/pull/543