nodeSelector causes defender deployment issues with twistlock-init

Bug

There are two issues:

1. console nodeSelector and defender nodeSelector should not necessarily be the same
2. the current nodeSelector is not copied into the defender secrete env variable correctly, which causes the API request for getting the defender ds manifest from the console to fail

For 2, the observed behavior is that the environment variable gets the value map[key:value] vs. key:value.

The workaround is to delete (or correct) the TWISTLOCK_NODE_SELECTOR env variable from the twistlock-defender secret during the init.