Update Release CodePipeline to update and upload agentVersionV2-<branch>.json file

[mye956]

Summary

This PR will modify our current release CodePipeline project to generate and copy over a new release config file called agentVersionV2-.json file which will be used in our release process in the near future. The <branch> refers to the tracking branch that will be used. (e.g. agentVersionV2-featureBranch.json), in this case it'll be dev.

(Note: This duplicates PR #3611 which has already been approved and merged. We'll have to manually update the CodePipeline project )

Implementation details

build-infrastructure/release-pipeline-stack.yml

• Added a new parameter called GithubSourceBranchName which will be passed in as an environment variable for the MakeJSON and Copy stages in order to refer to the tracking branch
• Updated the policy for the MakeJSON CodeBuild service role to have permission to access the release bucket

buildspecs/copy.yml

• Copying over the new agentVersionV2-.json file along with the rest of the configs/artifacts

buildspecs/release-config.yml

• Grabbing an existing/older version of agentVersionv2-.json file from the release bucket (Note: Will need to manually create one first)
• Updating the agentVersionv2-.json file only if there's a new agent release version

(Note: These changes will need to be manually applied to the CodePipeline project)

Testing

The release CodePipeline was replicated within my personal dev account along with these changes applied to it. No issues occurred while kicking off the release CodePipeline.

Description for the changelog

• Feature: Add new release config file called agentVersionV2-.json to our release CodePipeline project

Licensing

Related PR

• Update Release CodePipeline to update and upload agentVersionV2-<branch>.json file #3611

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