Use case: rerun a gtest against pre-built artifacts at an arbitrary revision with the same gtest switches no matter whether the test is disabled or not. (We are using historical post-commit build artifacts on Swarming/Isolate to rerun flaky tests and try to figure out when the flake started.)
  --gtest_filter=A.B --gtest_also_run_disabled_tests

Assumed A.B is already disabled by renaming to A.DISABLED_B (similar for DISABLED_A.B or DISABLED_A.DISABLED_B).

Currently without this change, the test is disabled, and won't be run by default unless you add to command line:
     * -- gtest_also_run_disabled_tests
     or
     * --gtest_filter=A.DISABLED_B --gtest_also_run_disabled_tests
In the json test result produced by base/test/launcher, the test is referred to as A.DISABLED_B in the "per_iteration_data".
(But it is referred to as A.B in "all_tests" and "disabled_tests", which is inconsistent.)

After this change, the test is still disabled, and won't be run by default unless you add to command line:
     * -- gtest_also_run_disabled_tests
     or
     * --gtest_filter=A.B --gtest_also_run_disabled_tests
In the json test result produced by base/test/launcher, the test is also referred to as A.B in the "per_iteration_data".