feat: added custom client PEM cert support

[petruki]

This pull request updates the way client certificates are handled for secure remote API connections. The main change is to support loading a PEM bundle containing both the client certificate and private key, with improved error handling and new tests to ensure correct behavior. Documentation has also been updated to clarify the new expectations for certificate handling.

Certificate handling improvements:

• The CertPath option now expects a PEM bundle that includes both the client certificate and private key, and the code loads this bundle using tls.LoadX509KeyPair. Errors encountered during loading are now surfaced to the caller. (remote.go, [1] [2]
• The httpClient() method now returns an error if the certificate bundle cannot be loaded, and this error is propagated through remote requests. (remote.go, remote.goL290-R343)

Testing enhancements:

• Added comprehensive tests in remote_transport_test.go to verify that the client correctly loads the certificate bundle, handles errors when the bundle is missing or invalid, and caches the HTTP client instance.

Documentation updates:

• Updated the documentation in README.md to clarify that CertPath should point to a PEM bundle containing both the client certificate and private key, and revised the feature description to reflect this. [1] [2]

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud