Expand documentation discussion about .serialized and global actors

[briancroom]

Description

We have a docs article Running tests serially or in parallel with some discussion about concurrent test execution and the .serialized trait. It would be lovely to see this expanded a little bit to also touch on things like:

• What can cause some tests to interfere with each other when they run concurrently (e.g. tests requiring exclusive access to shared global state, which can lead to problems even when using strict concurrency checking so that there are no formal data races)
• How isolating tests to a global actor (or calling out to code isolated to a global actor) can be used to help address this in some cases, without requiring .serialized
• Highlighting the way that tests interfering with each other in this way can provide an indication that non-test clients could also encounter similar problems, potentially suggesting that the API could be improved to help guard against the interference.

Additional information

No response