bug(projects): IntegrationJenkins late-inits null enableSslVerification as false #447

What happened?

In PR #435, IntegrationJenkins late-initializes enableSslVerification from JenkinsCIServiceProperties.EnableSSLVerification. client-go types that field as bool, not *bool. When GitLab returns "enable_ssl_verification": null, which it does for a newly created integration that never had the field set, the value decodes as false, and the provider writes enableSslVerification: false into the spec.

GitLab documents the default as true. A user who leaves the field unset ends up with an explicit false in the spec, and the next update sends false to GitLab. That may turn SSL verification off explicitly.

Seen live on GitLab 19.4.2-ee while testing #435. Not verified: whether GitLab itself treats null as true or false when it calls Jenkins.

Possible fix

• Skip late-init for enableSslVerification, or
• Ask client-go to type the field as *bool.