ENG-4023 - Separate MaxMind Reactor Status from rest of Threat Detection (#1321)

Problem:
To declare the license issue in a decent state, we must confront the fact that the Maxmind loader still has some issues. See https://linear.app/fusionauth/issue/ENG-4018/maxmind-loader-problems for what those are. We don't want to bite that off now, nor do we want to tell customers, etc. that "ALL our license code issues are fixed" with the develop branch, as is.

Solution:
Since improving those 2 issues may be broader in scope, in the meantime, it seems like a good idea to separate Reactor status values for items that have remote health involved, like Maxmind, from those that don't (CAPTCHA, etc. items that depend on threat detection). Breached password detection is already separated.

Author: wied03

openapi.yaml

@@ -5955,6 +5955,8 @@ components:
           "$ref": "#/components/schemas/ReactorFeatureStatus"
         expiration:
           "$ref": "#/components/schemas/LocalDate"
+        ipGeoLocation:
+          "$ref": "#/components/schemas/ReactorFeatureStatus"
         licenseAttributes:
           type: object
           additionalProperties: