ExtensionService::ReloadExtension disables the extension for disable_reason::DISABLE_RELOAD while it tries to reload the extension.  However, this reload can fail (e.g. for unpacked extensions), and, if it does, the extension winds up in a state of limbo - disabled for reload.  This eventually fixes itself on startup (where we check for extensions disabled for reload), but this isn't great, and causes oddities for the chrome://extensions page.

ExtensionService::ReloadExtension() should be able to handle reload failures, and subsequent calls should retry the reload, rather than immediately giving up.