Problem/Motivation
Whilst working on a project I want to be able to have tests trigger deprecation errors so that I can confirm that custom code is not using any deprecated core code. However, contrib code is likely to still be using deprecated APIs that trigger silenced deprecations.
Currently in order to do this the project patches the getSkippedDeprecations() in order to run deprecation tests and keep a record of our current technical debt (at this point it is all contribs technical debt).
Giving projects a better way to do this helps them prepare for new major version of Drupal.
Proposed resolution
Allow projects to set an environment variable that points to a file containing a list of addition deprecations to skip.
Projects can define a DRUPAL_DEPRECATION_SKIP_FILE that points to a file. The file contains a JSON encode array of deprecation messages to skip.
Remaining tasks
User interface changes
None
API changes
None
Data model changes
None
Release notes snippet
@todo