…ness (#170023)

Attempt at understanding #166190

I first thought the flakiness could be a regression in Elasticsearch,
but it turns out because I can only reproduce 90% of the time I got
"lucky" and found a previous ES commit where tests passed 3 times in a
row. On further investigation I was able to reproduce failures on
commits as old as July (before we even saw these failures) so ES is
unlikely to be the root cause 👎

Looking at our flaky test failure logs I found the first occurence
happened on 5 September on the branch for
#164959 (before it was merged) and
then subsequent failures on other branches and main happened within a
few hours after #164959 was merged
on 11 September.

However, nothing in #164959 should
have changed or impacted behaviour. To try to track down the cause this
PR is attempting to restorte `actions.test.ts` until before
#164959. Serverless tests will
continue to use `actions_test_suite.ts` but for classic we'll run the
old `actions.test.ts`.