Opt-in compatible compilers per local cache rather than per recipe

[foundry-markf]

Changelog: (Feature): Fixes issue #11722. Adding the ability to specify compatible compilers per local cache for all dependent packages, to avoid the need to modify their recipes. Use case is to ease the testing/migration of product builds to new compiler versions that produces ABI compatible code with existing packages in Artifactory.

cc @FnGyula

• [x] Refer to the issue that supports this Pull Request.
• [x] If the issue has missing info, explain the purpose/use case/pain/need that covers this Pull Request.
• [x] I've read the Contributing guide.
• [x] I've followed the PEP8 style guides for Python code.
• [ ] I've opened another PR in the Conan docs repo to the develop branch, documenting this one.

^{Note: By default this PR will skip the slower tests and will use a limited set of python versions. Check here how to increase the testing level by writing some tags in the current PR body text.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
0 out of 2 committers have signed the CLA.

:x: markfinal
:x: foundry-markf
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[memsharded]

This functionality is provided in 2.0 by the compatibility.py plugin. If such a plugin wants to load a yaml file from the cache to get its inputs to define compatibility, that is perfectly doable too, but it is better to keep the responsibilities de-coupled, settings.yml defines the space, compatibility.py defines the binary compatibility.

So I think we can close this PR, thanks very much for your contribution!