feat: allow user to skip privatization for specific methods/properties

[calebdw]

Hello!

There are occasions where final classes still need to have protected methods/properties (e.g., Laravel Models and the attributes/scope methods, see larastan/larastan#2334). Instead of simply skipping all Models, it would be great if the specific methods/properties can be skipped.

This PR adds the ability for the user to define a callback that is called with the property/method and the class reflection and allows the user to determine if anything should be skipped

Thanks!

[TomasVotruba]

Hey, I'm looking into this and adding callbacks to specific rule might trigger follow PRs with adding it everywhere.

Instead, this could be solved on a skip level. But performance would have to be considered first.
Still I'd like to keep the "skip" part of Rector as simple as possible.

In this specific example, the rule could be aware of the framework magic and behave propperly. We do the same with other rules, to take burden from the user having to spam the rector.php config to rule doing what it suppose to do.

Thanks for understanding 👍

[calebdw]

Sounds good, I wasn't sure if y'all would be okay with framework specific logic in the rector itself

[TomasVotruba]

In moderate amount, yes 😉