Add some constraints to allowlist

Summary:
Based on existing samples of soft errors, add existing constraints to the CI allowlist for CLI modifiers.
The allowlist is roughly divided into two sections. One for legal use cases and one for temporary migration use cases.
Roughly divided these based on observing the use cases and chatting with engineers that introduced the use of `--modifier` flags.

Reviewed By: Will-MingLun-Li

Differential Revision: D62679299

fbshipit-source-id: c4306f5fdcd58543f6a920f51862e467bf5e1e08

tests/e2e/configurations/cfg_constructor/test_cfg_constructors_inplace.py

@@ -57,7 +57,7 @@ async def test_cfg_constructor_with_target_modifiers(buck: Buck) -> None:
 )
 async def test_invoke_cfg_constructors_with_cli_modifier_validation(buck: Buck) -> None:
     env = {
-        "BUCK2_HARD_ERROR": "only=starlark_cli_modifier_fails_ci_allowlist_version_two"
+        "BUCK2_HARD_ERROR": "only=starlark_cli_modifier_fails_ci_allowlist_version_three"
     }
     await buck.cquery(
         "fbcode//buck2/tests/e2e/configurations/cfg_constructor/test_clear_package_modifiers_data/test_cfg_constructor_data:has_target_modifier",