TMR/Rate limit in compliance-test

[van-sprundel]

Describe the bug
This build job (specifically compliance-test) failed because of a TMR response.
It's the only job without a cache docker layers step, so adding this might be a fix.

Authenticating in the PR would also add double the rate limit (100 -> 200) per 6 hour.

[squell]

We've had some discussions locally; authenticating PR's seems like it would help us but not external contributors.

I think this is a classical "latency vs throughput" issue: we delibately removed that caching step this week since it shaved a substantial amount of time from the CI. Waiting for input from @rnijveld as well.