Research: Enhance templating capabilities for static definition template files

[MarkAckert]

See brief discussion here: #4512

Two variables were defined representing the same fact (is SSL enabled) because downstream static registration defines two fields containing the complementary values, and basic logic/conditions are unavailable:

  nonSecurePortEnabled: ${is_not_secure}
  securePortEnabled: ${is_secure}

Configmgr does support templating with logic, and would allow something like the below, which would be an improvement.

  nonSecurePortEnabled: ${{ is_not_secure ? true : false }}
  securePortEnabled: ${{ is_not_secure ? false : true }}

Note: is_secure would no longer be set as an env in this example.

This issue to research whether or not it makes sense to include configmgr as part of template rendering for static registration. Other rendering solutions not in scope.