Forbid the addition of new magic class methods

Is your feature request related to a problem?

Adding new magic methods such as __get and __set to WordPress Core should be discouraged unless necessary to fix existing dynamic class properties.
There is no good reason to use magic methods unless someone is writing an ORM library (which is not likely the case with WordPress Core).
PHP classes can almost always function just fine without them.

There have also been relatively recent examples of adding __get magic methods to new classes in WordPress versions 6.1 and 6.5 to provide backward compatibility. However, I'm not sure if that qualifies as a good reason to use magic methods in entirely new code.

Describe the solution you'd like

There could be a sniff that can take care of that (PrefixAllGlobals comes to mind).

class WP_Class {
    public function __get( $name ) { // This and similar magic methods should be detected and throw a linter error. Existing magic method usages should be allowed if necessary to fix existing dynamic class properties.
    }
}

I'm fine with this issue being closed without long explanations, as this idea may have already been explored and rejected.

Additional context (optional)

• I intend to create a pull request to implement this feature.

Start by reviewing the existing PrefixAllGlobals sniff, which the issue identifies as a possible model for detecting magic methods. Determine how the proposed rule should distinguish new magic methods from existing compatibility-related usages, then verify that the intended behavior is covered by the repository's sniff tests; the issue does not name specific files or tests.