chore(appsync): reorganize code base to improve readability

[BryanPan342]

[ISSUE]
aws-appsync library only had one file to host all the code. Hard to read and navigate because close to 2000 lines.

[APPROACH]
Segmented in the following manner:

• Data Sources
• Resolvers
• Keys
• GraphQL
• Mapping Templates

[NOTE]
File names and contents are subject to change as I continue to add to this construct.

---

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

Pull request has been modified.

[MrArnoldPalmer]

Definitely makes it much easier to navigate. Thanks! 🙏

[mergify]

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildProject6AEA49D1-qxepHUsryhcu
• Commit ID: d464ed1
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[skinny85]

Uhm. In general, we don't name files in camelCase. We use dash-case. So these files should be called data-source.ts, mapping-template.ts, etc.

[BryanPan342]

Uhm. In general, we don't name files in camelCase. We use dash-case. So these files should be called data-source.ts, mapping-template.ts, etc.

ah yes sorry! Code base is in camelCase so forgot. Will make a PR to fix it.