FINAL: Git storage option feature

[begonaguereca]

Summary:

This PR introduces the ability for the GEI CLI to upload archives to GitHub-owned storage using multipart uploads. To enable this, a new CLI option, --use-github-storage, has been added. This option allows users to explicitly specify that their archives should be uploaded to GitHub's managed storage instead of their own.

Key Features:

Multipart Upload Support: Leveraging multipart upload for reliable and efficient large file uploads. This ensures the robustness of the uploads, minimizing the chances of failure during transmission. We're investigating libraries to handle multipart uploads, but for now, this feature is not rolled by hand unless necessary.

New Option: --use-github-storage:

This option is required to upload archives to GitHub-owned storage and will be hidden until GitHub-owned storage reaches general availability (GA).
By default, archives are still uploaded to user-specified storage locations unless the --use-github-storage flag is explicitly set.

Motivation:

As discussed during our EDR, we want to allow users to utilize GitHub-owned storage as an option without making it the default. This approach lets us roll out GitHub-managed storage in stages and gather feedback while providing an explicit way to opt-in to this feature.

Check in BBS MigrateRepoCommandArgs removed, relating to changes in this PR: #1057

---

Take it out for a 🚗 :

*** Remember to export env variables***

export GH_SOURCE_PAT=<<PAT>>
export GH_PAT=<<PAT>> 

Migrating from GitHub Enterprise Server:

dotnet run --project src/gei/gei.csproj -- migrate-repo --github-source-org valet-testing --source-repo integration-tests --github-target-org octoshift-staging --target-repo YOU_ADD_NEW_NAME --use-github-storage true --ghes-api-url https://octoshift-ghe.westus2.cloudapp.azure.com/api/v3 --verbose

Successful migration_id: RM_kgHaACRlZjNiMmExMy02ZTRkLTQ0NWYtOTc4Yy05YTk1MTQ5NzE2OTk

Migrating from GitHub Enterprise Server- Multi part upload:

dotnet run --project src/gei/gei.csproj -- migrate-repo --github-source-org github-owned-storage --source-repo large-1-gib --github-target-org import-testing --target-repo YOU_ADD_NEW_NAME --use-github-storage true --ghes-api-url https://octoshift-ghe.westus2.cloudapp.azure.com/api/v3 --verbose

Successful migration_id: RM_kgDaACQ0MzZmN2RjMS0wNjk4LTRlYjctYmMzNy0wMTAxNGRhOTQ3YTU

---

Migrating from BBS:

Get info how to set up from slack channel 👍🏽

dotnet run --project src/bbs2gh/bbs2gh.csproj -- migrate-repo --bbs-project IM --bbs-repo codeowners-test --ssh-user bbs --ssh-private-key /Users/begonaguereca/.ssh/id_rsa_bbs_octoshift --use-github-storage true --bbs-server-url https://test-bbs-o.githubapp.com --github-org octoshift-staging --github-repo ADD_NEW_NAME --verbose

Successful migration_id: RM_kgHaACRhODI4NWRmZS0yNWM3LTQ1YjEtYTJhOC1jYmZjNTkxZDE0Mjk

---

Closes: https://github.ghe.com/github/octoshift/issues/8969

• Did you write/update appropriate tests
• Release notes updated (if appropriate)
• Appropriate logging output
• Issue linked
• Docs updated (or issue created)
• New package licenses are added to ThirdPartyNotices.txt (if applicable)

[github-actions]

Unit Test Results

825 tests   825 ✅  22s ⏱️
  1 suites    0 💤
  1 files      0 ❌

Results for commit 5aa0544.

♻️ This comment has been updated with latest results.

[ArinGhazarian]

I just looked at the integration tests and the reason they are failing is because the generate-script commands for gei and bbs2gh don't support the --use-github-storage option yet! What I recommend is to revert the INT test changes for now and add them back (in a separate PR) once we add the option to the generate-script commands.

[ArinGhazarian]

Looks great 🎉 🥇

Also don't forget to update the RELEASENOTES.md with a brief description of changes. It will get published as the release notes.

[github-actions]

Package	Line Rate	Branch Rate	Complexity	Health
gei	80%	71%	540	✔
ado2gh	84%	78%	627	✔
Octoshift	87%	76%	1298	✔
bbs2gh	79%	74%	666	✔
Summary	83% (7007 / 8394)	75% (1571 / 2090)	3131	✔