Run sbt commands in CI via a script

[jacobwinch]

What does this change?

Addresses #64 (comment). Moving all CI configuration into version control is generally desirable. For example, it will make it easier to review & apply all changes related to #64, as there will no longer be additional steps required in TeamCity.

I've deployed this to CODE and confirmed that it works as expected.

Once this PR is merged I will tidy up the TeamCity build configuration.

[jacobwinch]

When using the old version TeamCity wasn't picking up the build number correctly; this upgrade fixes that problem.

[jacobwinch]

This is currently running via this build step, which I've disabled for now.

[DavidLawes]

👍 makes sense to me

I notice that other projects we have (e.g. mapi, mobile-save-for-later-user-deletion) define their build steps in team city, as opposed to defining them in code. Is this a task we need on our backlog?

[jacobwinch]

I notice that other projects we have (e.g. mapi, mobile-save-for-later-user-deletion) define their build steps in team city, as opposed to defining them in code. Is this a task we need on our backlog?

It would be good to do this but it's not especially urgent. Hopefully we will start moving Scala projects to GitHub Actions in the next few months (we aren't recommending this to all teams just yet due to some performance concerns) and that migration will solve this type of problem too.