rabbit_feature_flags: Fix concurrent registry module reload

By calling code:delete() ourselves, we created a time window where there
is no registry module loaded between that call and the following
code:load_binary().

This meant that a concurrent access to the registry would trigger a load
of the initial uninitialized registry module from disk. That module
would then trigger a reload itself, leading to possible deadlock.

In fact, in code:load_binary(), the code server already takes care of
replacing the module atomically. We don't need to do anything.

0 files changed, 0 insertions, 0 deletions