Extract complex logic in build files into `buildSrc` so can be tested

[kggilmer]

From Aaron from related PR:

If you wanted to you could abstract this away into buildSrc which would allow tests. buildSrc allows custom code that is compiled BEFORE gradle configures the project. All types/functions/tasks/etc in buildSrc are made available to every gradle build script that is part of the project. People use this all the time to define library versions or custom tasks they want re-used, etc. It can also be used to define custom plugins (although more and more people are using composite builds for custom plugins).

Example from toolkits repo: https://github.com/aws/aws-toolkit-jetbrains/tree/master/buildSrc
Example from kotlinx.coroutines repo: https://github.com/Kotlin/kotlinx.coroutines/tree/master/buildSrc

[github-actions[bot]]

This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to provide a comment or open a new issue.

[aajtodd]

Closing in favor of any work we do to consolidate build logic to https://github.com/awslabs/aws-kotlin-repo-tools/

[github-actions[bot]]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.