Add scripts to prepare test GitHub Enterprise Server on AWS

[dmytro-ndp]

Is your task related to a problem? Please describe

https://github.com/che-incubator/git-srv/blob/main/github/deploy_github.adoc is actually describing steps to install GitHub Enterprise Server using VirtualBox on local machine, which can't be used in automated PR check using GitHub action.

Also, installation using VirtualBox is flaky and resource consuming + requires support of public IP and DNS server to configure subdomain isolation.

Describe the solution you'd like

Add automation scripts to repo [1] to install GitHub Enterprise Server on AWS for testing purpose.

[1] https://github.com/che-incubator/git-srv/blob/main/github/deploy_github.adoc

Describe alternatives you've considered

No response

Additional context

Related issues:

• Testing Git zero-config flow as PR checks #21753
• https://issues.redhat.com/browse/CRW-3509

[vinokurig]

The instructions are already written by GitHub https://docs.github.com/en/enterprise-server@3.7/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws

[dmytro-ndp]

@vinokurig: thanks for the link.

Do you think https://github.com/che-incubator/git-srv/blob/main/github/deploy_github.adoc is also useless having https://docs.github.com/en/enterprise-server@3.7/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware ?

[vinokurig]

I don't think so, the che-incubator instructions describe a way to install the server on virtualbox environment.

[dmytro-ndp]

@vinokurig: got it.

The issue is renamed correspondingly.

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.