The newer storage backend keeps the first config path it resolved and logs the conflict.
What's wrong with this entry?
Building the v5 storage backend accepts a global config path and a file-serving declaration from the host, and if the global config path had already been resolved before the host supplied one, the first answer is kept and the reason is logged. Whether the backend was built or fell back is still reported under storage_v5_backend, which also gates entry.
global config file already resolved to the handed path before the host handed it; keeping that first answer
Strings lifted out of the shipped bundle, so the claim above can be checked against them.