Rebase to Horde 0.9.0

[studzien]

This rebases our changes to Horde 0.9.0 (the latest version).

Two additional changes:

1. This PR was reverted -- 8fbaf33
   This change was incomplete and incorrect in the scenario when a process crashed on the same host. The restarted process might not have been re-added to the registry.
2. From horde's master - this PR was reverted - 0d8c9ae
   That's because we still care about the synchronicity (the PR mentioned in point 1) of the auction process start (that's what OTP's processes rely on), but it's not susceptible to the issue introduced in Add process added to local Register synchronously #2. We also don't care about the scenario that the PR fixed initially because we don't start two processes with the same key.

When this is approved, I will force push to master.

[PranavVadrevu]

Just for my understanding:

This change was incomplete and incorrect in the scenario when a process crashed on the same host. The restarted process might not have been re-added to the registry

Why would the restarted process not be added to the registry if doing this synchronously @studzien?

[studzien]

Just for my understanding:

This change was incomplete and incorrect in the scenario when a process crashed on the same host. The restarted process might not have been re-added to the registry

Why would the restarted process not be added to the registry if doing this synchronously @studzien?

So I believe the problem was here, so essentially when another add operation was processed on the same node, it was ignored. I can't remember exactly, but I guess I wrongly assumed that handling this in register only would do the job.

I tested this by running this test:
https://github.com/Whatnot-Inc/whatnot_live/blob/main/test/medium/da/auction_test.exs#L408-L436
with and without sleep.