Bump content-entity's latest release

[Divs-B]

We have got latest release of content-entity after implementing gha-scala-library-release
This PR will bump that version and test as well.

[gu-scala-library-release]

@Divs-B has published a preview version of this PR with release workflow run #13, based on commit cb6c4e6:

4.0.2-PREVIEW.db-rttest-content-entity-release.2024-03-26T1749.cb6c4e64

Want to make another preview release?

Click 'Run workflow' in the GitHub UI, specifying the db-rt/test-content-entity-release branch, or use the GitHub CLI command:

gh workflow run release.yml --ref db-rt/test-content-entity-release

Want to make a full release after this PR is merged?

Click 'Run workflow' in the GitHub UI, leaving the branch as the default, or use the GitHub CLI command:

gh workflow run release.yml

[Divs-B]

We have tested preview release in content-api-model which later has got tested in apple-news .
all working as expected.

[rtyley]

Great!

To save you a bit of time, I'll merge this and generate a new release...

[rtyley]

Oh no :( the release process failed for Sonatype:

2024-03-27 14:33:57.077Z error [Sonatype] 
wvlet.airframe.http.HttpClientException: [401: Unauthorized]
	at wvlet.airframe.http.HttpClientException$.requestFailure(HttpClientException.scala:72)
	at wvlet.airframe.http.HttpClientException$.classifyHttpResponse(HttpClientException.scala:119)
	at wvlet.airframe.http.client.HttpClients$.$anonfun$baseHttpClientRetry$1(HttpClients.scala:43)
	at wvlet.airframe.control.Retry$RetryContext.classifyResult(Retry.scala:268)
	at wvlet.airframe.control.Retry$RetryContext.$anonfun$runAsyncWithContext$3(Retry.scala:3[30](https://github.com/guardian/content-atom/actions/runs/8453474431/job/23156437974#step:5:31))
	at wvlet.airframe.rx.RxRunner.$anonfun$run$16(RxRunner.scala:233)
	at scala.util.Try$.apply(Try.scala:213)

I've not seen a failure at that point for quite some time... obviously, it's not the fault of this PR, but tidying it up will be a bit tiresome due to the guardian/gha-scala-library-release-workflow#33 problem.

I'll try publishing a different project, to see if that succeeds.

[rtyley]

So releasing etag-caching worked fine:

...I think this might mean that the release failure here is just Sonatype being flakey?? I will try doing a new release on content-atom.

[rtyley]

A second attempt at release succeeded, with no significant changes to the content-atom repo at all:

...so I guess it was just Sonatype being flakey (which isn't great...!).

Surprisingly, despite guardian/gha-scala-library-release-workflow#33, I didn't have to disable compatibility checking - as it was already absent! We need to add that back in...

[Divs-B]

Thanks @rtyley for checking the release. It does looks like i missed adding compatiblity check when adopting release process. will do it in the PR 👍