Not possible to override Prettier config when using recommended ESLint ruleset

[aduth]

Previously: #20509, #21602

Steps to Reproduce:

1. Create a custom .prettierrc with own configuration values that differ from WordPress default (e.g. "printWidth": 100).
2. Extend @wordpress/eslint-plugin recommended configuration in ESLint
   • { "extends": "plugin:@wordpress/eslint-plugin/recommended" }
3. Run ESLint

Expected: My Prettier configuration values take precedence.
Actual: The WordPress default config values are always used.

The intention of #20509 is clear in its title that the default should take effect "when no config found". If a configuration is found, it should either be used verbatim, or merged with the WordPress default values.