GitHub Pages infra: account, Action listener

[Lsquared13]

@Lsquared13 and I spoke today about how the final GitHub pages offering might work. Much of the development would be within the aws-abi-clerk Lambda function, but there would also be some support infrastructure built into the terraform:

1. The initial CodePipeline created by Lambda function needs to be able to use a company GitHub account to place a commit in the customer's repository
2. We may need to create a Lambda listener for a GitHub action so we can respond to branch changes without maintaining a constant pipeline.

[Lsquared13]

CodePipeline doesn't have a GitHub Deploy action so we'll need to write a Lambda function to do it. It seems like there are some GitHub SDKs for Node.

So the initial build pipeline should look like this:

• Source: S3 (Dappseed)
• Build: run dappsmith
• Invoke: Lambda function commits artifacts to GitHub repo

The deployment pipelines should look like this:

• Source: GitHub (Customer repository)
• Build: create-react-app
• Deploy: S3 (Website bucket)

[Lsquared13]

I'm getting the impression that Octokit is the better maintained SDK. Docs are here

github-api is another option but it seems to have less activity and be less well organized

These instructions are for a .NET port of Octokit, but they seem to detail the commit process pretty well.

[Lsquared13]

Bumped the listener into another issue