Please address the comments from this code review:

## Overall Comments
- Consider avoiding the hard-coded "FORCE_COLOR" string in `default_config` by centralizing it as a constant or reusing an existing helper, so changes to the env var name only need to happen in one place.

## Individual Comments

### Comment 1
<location path="tests/meltano/core/logging/test_logging_utils.py" line_range="74" />
<code_context>
             False,
             "\x1b[2m2021-01-01T00:00:00Z\x1b[0m [\x1b[32minfo     \x1b[0m] \x1b[36mmeltano     \x1b[0m \x1b[1mtest                          \x1b[0m",  # noqa: E501
             id="colored-non-tty-force-color",
-            marks=(
-                pytest.mark.xfail(
</code_context>
<issue_to_address>
**suggestion (testing):** Add an explicit test case for `FORCE_COLOR` + `NO_COLOR` precedence

With `colored-non-tty-force-color` now enabled, please also add a test that sets both `FORCE_COLOR` and `NO_COLOR` and asserts that colors are disabled. This will encode the intended precedence and guard against regressions where `FORCE_COLOR` incorrectly wins over `NO_COLOR`.

Suggested implementation:

```python
            False,
            "\x1b[2m2021-01-01T00:00:00Z\x1b[0m [\x1b[32minfo     \x1b[0m] \x1b[36mmeltano     \x1b[0m \x1b[1mtest                          \x1b[0m",  # noqa: E501
            id="colored-non-tty-force-color",
        ),
        pytest.param(
            LogFormat.uncolored,
            False,
            "2021-01-01T00:00:00Z [info     ] meltano     test                          ",
            id="uncolored-non-tty-force-and-no-color",
        ),
        pytest.param(
            LogFormat.uncolored,

```

To fully implement the precedence test, you should:
1. Ensure this new `pytest.param` is included in the same parametrized test that configures environment variables. Mirror the pattern used by other cases (e.g., existing `NO_COLOR` or `FORCE_COLOR` cases) to set both `FORCE_COLOR` and `NO_COLOR` for this `id="uncolored-non-tty-force-and-no-color"` case.
2. If environment setup is driven by parametrized marks (like `marks=pytest.mark.parametrize` or custom marks that inject `env`), add the appropriate mark so that `FORCE_COLOR` and `NO_COLOR` are both set in the environment for this case, and verify that the logging output matches the uncolored string above.
</issue_to_address>