Modify the BASE_FEATURE define

[uazo]

it happens that sometimes wiggle makes unexpected changes, for example:

@@ -1525,8 +1525,8 @@ BASE_FEATURE(kUseWebAppDBInsteadOfExternalPrefs,
              base::FEATURE_ENABLED_BY_DEFAULT);
 
 BASE_FEATURE(kWebAuthFlowInBrowserTab,
-             "WebAuthFlowInBrowserTab",
-             base::FeatureState::FEATURE_DISABLED_BY_DEFAULT);
+             "WebAuthFlowInBrowserTab",                         // disable by default
+             base::FeatureState::FEATURE_DISABLED_BY_DEFAULT);  // in bromite
 const base::FeatureParam<WebAuthFlowInBrowserTabMode>::Option
     web_auth_flow_modes[] = {

becomes

@@ -1560,8 +1560,8 @@ BASE_FEATURE(kUseWebAppDBInsteadOfExternalPrefs,
              base::FEATURE_ENABLED_BY_DEFAULT);
 
 BASE_FEATURE(kWebAuthFlowInBrowserTab,
-             "WebAuthFlowInBrowserTab",
-             base::FeatureState::FEATURE_ENABLED_BY_DEFAULT);
+             "WebAuthFlowInBrowserTab",                         // disable by default
+             base::FeatureState::FEATURE_ENABLED_BY_DEFAULT);  // in bromite
 const base::FeatureParam<WebAuthFlowInBrowserTabMode>::Option
     web_auth_flow_modes[] = {

notice disabled to enabled

To solve this I should create a BASE_FEATURE_ALWAYS_DISABLED so that it is not confused

seen in #286

[uazo]

To solve this I should create a BASE_FEATURE_ALWAYS_DISABLED so that it is not confused

wouldn't work anyway.
the problem is in wiggle, which would automatically modify that too in that case.
assess whether it is possible to set it when loading flags

[uazo]

uazo/cromite#403