feat(StdLib): Go v0.0.1 release

[ShubhamChaturvedi7]

Issue #, if available:

Description of changes:

Initial release based on MPL 1.8.0.

Files to be reviewed:
README.md
LICENSE
CHANGELOG.md
externs (Copied over from checked-in code / Optional)
Makefile (Copied over from checked-in code / Optional)
go.mod (Copied over from checked-in code / Optional)

Other files are polymorphed files.
Squash/merge commit message, if applicable:

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[seebees]

LGTM

[rishav-karanjit]

Some overall things:

1. Can we have a MCM to see how this fits in?
2. How do we know if this code runs as it ran when it was inside runtime/go? Knowing this before releasing would help MCM technician/requester.
3. What tag are we adding to do this release?

[ShubhamChaturvedi7]

Some overall things:

1. Can we have a MCM to see how this fits in?

2. How do we know if this code runs as it ran when it was inside runtime/go? Knowing this before releasing would help MCM technician/requester?

3. What tag are we adding to do this release?

MCM is answered here: https://amzn-aws.slack.com/archives/G01813NHQBD/p1736791637977939?thread_ts=1736559063.433249&cid=G01813NHQBD

1. MCM is planned later after this release. It'd be futile to have an MCM which doesn't cover all the steps and we are still discovering the steps.
2. Ran go build
3. Mentioned in the description v0.0.1

[rishav-karanjit]

Mentioned in the description v0.0.1

Shouldn't it be prefixed with path from the runtime?
ref: https://go.dev/ref/mod#vcs-version

If a module is defined in a subdirectory within the repository, that is, the module subdirectory portion of the module path is not empty, then each tag name must be prefixed with the module subdirectory, followed by a slash.

[rishav-karanjit]

Talked offline. The GitHub tag is prefixed with subdirectories.

Non blocking but it could be great if we could have a CI test to do go build to check if the copied code works correctly.

LGTM

[ShubhamChaturvedi7]

Mentioned in the description v0.0.1

Shouldn't it be prefixed with path from the runtime? ref: https://go.dev/ref/mod#vcs-version

If a module is defined in a subdirectory within the repository, that is, the module subdirectory portion of the module path is not empty, then each tag name must be prefixed with the module subdirectory, followed by a slash.

Are you talking about git tag or Go tag? The git tag would be something like git tag smithy-dafny-standard-library/v0.0.1-alpha (in this case releases/go will be prefixed as well), and go version tag v0.0.1 so that users can do go get [email protected].

Here's an example to explain this: https://github.com/ShubhamChaturvedi7/aws-cryptographic-material-providers-library-go/releases/tag/smithy-dafny-standard-library%2Fv0.0.1-alpha