Respect Zowe rejectUnauthorized setting

[Tannex]

Summary

• accept Zowe zosmf profiles that explicitly set rejectUnauthorized: false
• scope disabled certificate verification to the cloned HTTP transport for that Zowe session
• retain certificate verification by default and when rejectUnauthorized is true
• document the man-in-the-middle risk and recommend trusting the z/OSMF CA instead

Root cause

The native Zowe configuration loader parsed rejectUnauthorized, but rejected HTTPS profiles when the resolved value was false. This differed from Zowe's configured behavior and prevented access to z/OSMF installations with noncompliant or privately managed certificates.

User impact

Profiles that explicitly opt out of certificate verification now work with cq. Profiles that omit the setting continue to verify certificates by default.

Validation

• go test ./...
• go test -race ./...
• go vet ./...
• Darwin arm64 test-binary cross-compilation
• Windows amd64 test-binary cross-compilation