[csharp-netcore]Http signing for csharp-netcore sdk

Created by: Ghufz

Implemented the HTTPSigning Auth for CSharp SDK. It provides RSA Key support and ECDSA key support (for ECDSA key support it require dotnetcore3 and above)

Example to configure HTTPSigning configuration

Configuration config = new Configuration();
config.BasePath = "https://xyz.com";

HTTPSigningConfiguration httpSigning = new HTTPSigningConfiguration()
{
	KeyId = "xxxxxxx6876789ac747/5ee09xxxx4612d31a62c01/5ee09a1d7564612d31a6xxxx",
	KeyFilePath = "C:\\SecretKey.txt",
	HTTPSigningHeader = new List<string>() { "(request-target)", "Host", "Date", "Digest" }
};

config.HTTPSigningConfiguration = httpSigning;

//After create the instance of API and pass the configuration object.
//call the required method on Api instance to accomplished the task.

var apiInstance = new PetApi(config);
var result = apiInstance.GetPetById("223333");

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• If contributing template-only or documentation-only changes which will change sample output, build the project beforehand.
• Run the shell script ./bin/generate-samples.shto update all Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master. These must match the expectations made by your contribution. You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*. For Windows users, please run the script in Git BASH.
• File the PR against the correct branch: master
• Copy the technical committee to review the pull request if your PR is targeting a particular programming language. @wing328