Enable TCP keep alive for CRT HTTP client if configured

[eckardnet]

Motivation and Context

I configured keep alive for http crt client, but it din't seem to have an effect.
I did not find a way to set this boolean to true in SocketOptions in any other way.

Modifications

Set boolean to true if keep alive config is not null.

Testing

no testing

Screenshots (if appropriate)

Types of changes

• [ x] Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• [x ] I confirm that this pull request can be released under the Apache 2 license

[zoewangg]

This seems like a regression on CRT side introduced in awslabs/aws-crt-java#750. Setting it to true was not required before. (Edit: nvm, I misspoke)

[zoewangg]

Apologies for the delay. LGTM, triggering builds

[eckardnet]

Do I have to do anything more now?

[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 SonarCloud

[zoewangg]

@all-contributors please add @eckardnet for code

[allcontributors]

@zoewangg

I've put up a pull request to add @eckardnet! 🎉

[eckardnet]

Thank you :-)