Add support for including extra_chain_cert with p12

[nparker-tc]

Summary of feature

We ran into an integration where the partner required the full certificate chain included with SSL requests. Adding this support in HTTParty allows the option to include the full certificate chain utilizing the existing data from the p12 certificate. This feature has been included in Net::HTTP since Ruby 3.0. I have added a safety check to prevent compatibility issues to ensure it is only accessible when the extra_chain_cert= method is available on the Net::HTTP instance.

Techinical Details

• Added option to determine if the full certificate chain should be included. Defaults to false
• Add support in connection_adapter to include the full certificate chain if the option is enabled, p12 is being used, and Net::HTTP supports including the certificate chain
• Added specs for both new methods

[jnunemaker]

Looks good. I've not used this and know nothing about it but I'll merge after CI passes.

[nparker-tc]

@jnunemaker Wow thanks for the quick response! I will re-try locally the 2.7 build and get it fixed. Appreciate it!

[nparker-tc]

@jnunemaker

The previous issue was with the way the specs were written. It would run the expectation regardless of whether it was supported on that ruby version or not. In the new specs, both scenarios are checked for the supported and unsupported ruby versions and validate the behavior for both.

Ruby 3.0 build:

Ruby 2.7.8 build:

[jnunemaker]

@nparker-tc 2.7 is failing. Any ideas why? I didn't look closely.

[nparker-tc]

@nparker-tc 2.7 is failing. Any ideas why? I didn't look closely.

@jnunemaker Is it still? I think it is currently awaiting on a workflow approval for a new build with the updated specs. It failed previously based on the way the specs were written.
More details are in this comment: #802 (comment)
Fix is in this commit: a636119
Workflow pending: https:/jnunemaker/httparty/actions/runs/9962038185