Reland "Write did-run to registry asynchronously."

In this attempt, only run asynchronously from the renderer launch, not
from the DLL loading, since the thread pool does not exist during
DLL loading.

This is a reland of commit 74344b22ad439a57f6f99453c83b9b9ed59813d8
Patchset 1 is the original change.

Original change's description:
> Write did-run to registry asynchronously.
>
> My understanding is that generally we allow registry writes on the main
> sequence. However, they can take time if some other application is
> calling RegFlushKey (which blocks modifications to the entire hive), or
> something else is affecting registry write performance on the machines.
>
> Since neither the sequencing nor outcome of recording did-run is
> relevant to the callers, making the operation non-blocking seems easy
> enough.
>
> Fixed: 1509160
> Change-Id: I3d760bbe13c2b6427705c02524441c1ea0ce87b1
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5164608
> Auto-Submit: Joshua Pawlicki <waffles@chromium.org>
> Reviewed-by: Erik Chen <erikchen@chromium.org>
> Reviewed-by: Greg Thompson <grt@chromium.org>
> Commit-Queue: Joshua Pawlicki <waffles@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1244641}

Change-Id: Iccccd1ec8b1275362d826ac213a35341a34b87a6
Fixed: 1509160
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5181894
Reviewed-by: Erik Chen <erikchen@chromium.org>
Commit-Queue: Joshua Pawlicki <waffles@chromium.org>
Reviewed-by: Greg Thompson <grt@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1245268}