GC/nogc status in docs

[SealabJaster]

On Monday, 13 July 2020 at 11:16:07 UTC, aberba wrote:
> The
>> From what I have read,...
> is all over the place.

Perhaps we need a sort of "mythbusting" page.

"
MYTH: D's GC will **randomly** cause pauses in your program!

FACT: D's GC only decides if it needs to run during allocations, 
and collections can be manually disabled for hot 
paths(GC.disable/GC.enable), as well as forced prematurely 
(GC.collect).
"

And the like.