chore: update defaults for apiml v3

[pablocarle]

• Tests for the changes have been added (for bug fixes / features)
• Necessary documentation (if appropriate) have been added / updated
• DCO signoffs have been added to all commits, including this PR

PR type

• Bugfix

Changes proposed in this PR

• Set zaas component as enabled by default in defaults.yaml. This component is required for API ML to work.
• Remove unsupported internal connector settings in v3.

Does this PR introduce a breaking change?

• Yes
• No

[github-actions]

build 6109 SUCCEEDED.
Link to workflow run: https://github.com/zowe/zowe-install-packaging/actions/runs/10954913130

[pj892031]

I guess also those attributes for GW doesn't make sense anymore:

    auth:
      provider: zosmf
      zosmf:
        jwtAutoconfiguration: jwt
        serviceId: ibmzosmf
    authorization:
      endpoint:
        enabled: false
      provider: ""

[github-actions]

Test workflow 5435 is started.
Running install test: Convenience Pax
The zowe artifact being used by this test workflow: libs-snapshot-local/org/zowe/3.0.0-PR-4004/zowe-3.0.0-pr-4004-6109-20240920072110.pax
Running on machine: zzow07
Result: SUCCESS
Link to workflow run: https://github.com/zowe/zowe-install-packaging/actions/runs/10954989567

[github-actions]

build 6120 SUCCEEDED.
Link to workflow run: https://github.com/zowe/zowe-install-packaging/actions/runs/10962502399

[github-actions]

build 6121 SUCCEEDED.
Link to workflow run: https://github.com/zowe/zowe-install-packaging/actions/runs/10962513413

[MarkAckert]

I guess also those attributes for GW doesn't make sense anymore:

    auth:
      provider: zosmf
      zosmf:
        jwtAutoconfiguration: jwt
        serviceId: ibmzosmf
    authorization:
      endpoint:
        enabled: false
      provider: ""

These attributes are also in the example-zowe.yaml file. Do you mean the attributes don't make sense in either place, or don't make sense in defaults because they're already in the example-zowe file?

[github-actions]

Test workflow 5444 is started.
Running install test: Convenience Pax
The zowe artifact being used by this test workflow: libs-snapshot-local/org/zowe/3.0.0-PR-4004/zowe-3.0.0-pr-4004-6121-20240920160827.pax
Running on machine: zzow06
Result: SUCCESS
Link to workflow run: https://github.com/zowe/zowe-install-packaging/actions/runs/10962628580

[github-actions]

Test workflow 5445 is started.
Running install test: Convenience Pax
The zowe artifact being used by this test workflow: libs-snapshot-local/org/zowe/3.0.0-PR-4004/zowe-3.0.0-pr-4004-6120-20240920161016.pax
Running on machine: zzow06
Result: FAILURE
Link to workflow run: https://github.com/zowe/zowe-install-packaging/actions/runs/10962671735

[MarkAckert]

I guess also those attributes for GW doesn't make sense anymore:

    auth:
      provider: zosmf
      zosmf:
        jwtAutoconfiguration: jwt
        serviceId: ibmzosmf
    authorization:
      endpoint:
        enabled: false
      provider: ""

These attributes are also in the example-zowe.yaml file. Do you mean the attributes don't make sense in either place, or don't make sense in defaults because they're already in the example-zowe file?

The changes are fine as-is in example-zowe.yaml