chore:Golang release staging branch/encryption sdk/0.4.0 (#907)

Co-authored-by: GitHub Actions <actions@github.com>
Co-authored-by: Shubham Chaturvedi <scchatur@amazon.com>

chore: uncomment release steps for dotnet (#879)

chore(go): Release encryption-sdk Go module 0.3.0 (#838)

Co-authored-by: GitHub Actions <actions@github.com>
Co-authored-by: Shubham Chaturvedi <scchatur@amazon.com>

chore: dotnet 4.1.1 release using only mpl-1.7.6 (#833)

Co-authored-by: Andy Jewell <ajewell@amazon.com>

feat(Go): esdk-go release v0.2.0 (#769)

Co-authored-by: Shubham Chaturvedi <scchatur@amazon.com>

Merge branch 'mainline' into Go_Upgrade

feat: Go ESDK v0.0.1 release (#741)

Co-authored-by: Shubham Chaturvedi <scchatur@amazon.com>

feat: Go ESDK v0.0.1 release (#741)

Co-authored-by: Shubham Chaturvedi <scchatur@amazon.com>

chore(release): change PackageReference of MPL (#654)

fix(ESDK): Head Auth logic and HKDF's info parameter (#621)

The ESDK-NET’s Message Header AAD
incorrectly appended two empty bytes
when using the DefaultCMM.
The HKDF invocation of non-committing algorithm suites
failed to include the Message ID in the info parameter.

Neither of these issues 
effect the security of messages 
written by the 4.0.0 release.

However, 
these messages diverge 
from the Encryption SDK Message Specification.
Thus:

* ESDK-NET v4.0.0 writes messages that only ESDK-NET v4.0.0 and greater can read.
* ESDK-NET v4.0.0 is ONLY able to read messages that are written by ESDK-NET v4.0.0

These issues are fixed in 4.0.1, 
which writes messages according to the Encryption SDK Message Specification,
and are interoperable with other implementations of this library.

The option NetV4_RetryPolicy can be use to decrypt v4.0.0 messages.
See AwsEncryptionSDK/runtimes/net/Examples/NetV4_0_0Example.cs on how to use the NetV4_RetryPolicy
and details on distributed applications.