Automate Tarball Release and Publish to Conda-Forge

[harvenstar]

Issue #, if available:

Description of changes:

This PR introduces automation for the release workflow of the SageMaker Code Editor tarball, as well as publishing to conda-forge:

The package and tarball are now versioned according to a defined versioning strategy.
Tarball generation is triggered automatically upon creation of a version tag via GitHub Actions.
A new GitHub Action is added to create a pull request for conda-forge feedstock, updating it with the latest tarball version.
The design documentation is updated to describe the versioning strategy, tarball generation, and conda-forge update process.
This automation streamlines the release cycle and minimizes manual intervention for both artifact generation and conda-forge publication.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[Copilot]

Pull Request Overview

This PR adds GitHub Actions workflows to automate the versioned release of the SageMaker Code Editor tarball and to publish updates to the conda-forge feedstock.

• Introduces a release.yml workflow triggered on version tag pushes to build a tarball, publish a GitHub Release, and update the conda-forge feedstock.
• Adds a codebuild-ci.yml workflow to run AWS CodeBuild checks on pull requests against main.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
.github/workflows/release.yml	New automated release workflow for tarball build/publish and feedstock updates
.github/workflows/codebuild-ci.yml	New pull-request CI workflow invoking AWS CodeBuild

Comments suppressed due to low confidence (4)

.github/workflows/release.yml:5

• [nitpick] This comment refers to the main branch but the trigger is on tag pushes; please update it to describe that the workflow runs on tag pushes (e.g., "Triggers on version tag pushes").

  # Triggers the workflow on updates to the "main" branch which include a version tag

.github/workflows/release.yml:71

• [nitpick] Hard-coding the workspace path may break if the repository name or workspace root changes; consider using the $GITHUB_WORKSPACE environment variable instead of a fixed path.

          git config --global --add safe.directory /__w/sagemaker-code-editor/sagemaker-code-editor

.github/workflows/release.yml:130

• [nitpick] This comment is duplicated immediately above; please remove the redundant line to keep the file concise.

            # Updates the meta.yaml file in the cloned feedstock repository

.github/workflows/codebuild-ci.yml:30

• The source-version-override syntax with head^{...} may not be interpreted correctly by CodeBuild; consider specifying either the PR ref (refs/pull/.../head) or directly using the commit SHA without the ^{} notation.

          source-version-override: 'refs/pull/${{ github.event.pull_request.number }}/head^{${{ github.event.pull_request.head.sha }}}'