[2201.5.x] Add support for configuring server name to be used in the SSL SNI extension

[Bhashinee]

Purpose

Add support for configuring the server name to be used in the SSL SNI extension.
Related issue: ballerina-platform/ballerina-library#7435

Introduced a new field named serverName in the secureSocket config under ClientConfiguration.

Examples

http:ClientConfiguration clientConf = {
    secureSocket: {
        cert: {
            path: common:TRUSTSTORE_PATH,
            password: "ballerina"
        },
        serverName: "localhost"
    }
};

@shafreenAnfar @TharmiganK I used serverName as the field name as it is the name that has been used in the Go language as well. If you have any concerns with the name, please suggest.

Checklist

• Linked to an issue
• Updated the changelog
• Added tests
• Updated the spec
• Checked native-image compatibility
• Checked the impact on OpenAPI generation

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud