Enable configuration options in twistlock.cfg to be customizable via values.yaml

Currently the twistlock.cfg file has hardcoded settings, meaning that it is not customizable by default. There are some options that would be nice to be able to set via values.yaml, including SELinux and disaster recovery settings.

There are two approaches we could take:

• Allow overriding on ENVs for the deployment, use these ENVs as the values in the configmap
• Use helm templating of values in the config using {{ default <existing cfg value> .Values.<some override>}}

Quick evaluation:

ENVs:

• doesn't require us to enumerate all options, just add a generic ENV value passthrough
• makes it unclear to end user that these options are available - downside...

Helm templating:

• requires us to enumerate explicitly available options
• more direct to use helm templating instead of envs
• more clear to the end user that the options are available

I lean towards helm templating, but if there's additional upside/downside to either option definitely evaluate and choose what makes the most sense.