Implementing gha-scala-release-process in this library.

[Divs-B]

What does this change?

Simplify and automise the release process on Copip libraries by implementing gha-scala-library-release-workflow that is more secured, quicker, easy to deploy and removes boilerplate code from build.sbt, release.yml as well.

We granted secerts access to this repo via adding the repo name in github-secret-access
https://github.com/guardian/github-secret-access/pull/36

steps mentioned in Configuration has been followed.
https://github.com/guardian/gha-scala-library-release-workflow/blob/main/docs/configuration.md

How to test

By making release once the PR is reviewed and merged.

How can we measure success?

Released version and details should be available to be used by clients.

[rtyley]

HI @Divs-B ! A lot of this looks good, but one thing that is currently missing from this project is CI - nothing is running the tests!

Could you do a separate PR first to introduce CI on this repo, so we can see more easily if we're breaking anything? The CI should probably be setup like we did with content-api-client-aws:

• https://github.com/guardian/content-api-client-aws/blob/main/.github/workflows/ci.yml
• https://github.com/guardian/content-api-client-aws/blob/8b90f40dc0a99cd5ca21ed344f8672402de19d0d/build.sbt#L13-L14

[github-actions]

Test Results

 4 files  ±0   4 suites  ±0   0s ⏱️ ±0s
11 tests ±0  11 ✅ ±0  0 💤 ±0  0 ❌ ±0 
22 runs  ±0  22 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 6751844. ± Comparison against base commit b2f56f4.

♻️ This comment has been updated with latest results.

[rtyley]

Looks good to me!

It looks like https://github.com/guardian/facebook-newstab would be a good project to check that thrift-serializer functionality was still working, as it has https://github.com/guardian/facebook-newstab/blob/389db27a205f6888236d8e726da3cd056838e1ed/src/test/scala/com/gu/facebook/ContentDecachedEventSerializerSpec.scala, which at least partially exercises some of the functionality of the library.