Missing z/OSMF configuration creates an invalid static definition for APIML

[richard-salac]

Describe the bug
When z/OSMF configuration is missing in the zowe.yaml, the launcher generates an invalid api static definition for zosmf causing the APIML to log an error on startup.

related to #4790

To Reproduce
Steps to reproduce the behavior:

1. Remove the OSMF section form the zowe.yaml
2. Start Zowe
3. APIML produces an error message in the log

Expected behavior

• z/OSMF static definition is created only when the zOSMF section is defined in the zowe.yaml
• if the zOSMF is not present in the zowe.yaml, the old static definition for zosmf is removed

Additional context
When APIML is configured with SAF authentication provider, there is no requirement for z/OSMF. However several users reported APIML logging errors after they removed the zOSMF section from their zowe.yaml. The api static definition for APIML is still created and contains invalid values:

workspace/api-mediation/api-defs/apiml.zosmf_static_definition_yaml_template..yaml

services:
    - serviceId: ibmzosmf
      title: IBM z/OSMF
      description: 'IBM z/OS Management Facility REST API service. Once configured you can access z/OSMF via the API gateway...'
      catalogUiTileId: zosmf
      instanceBaseUrls:
        - https://:/
      homePageRelativeUrl:  # Home page is at the same URL