Extend dangerous attribute methods with dangerous methods from Object

[fatkodima]

Fixes #45879 (see there for more details).

Another option would be not to exclude the methods that were inherited, but then have a small exclusion list for Object methods that are unlikely to be a problem and are common names (e.g. Object#display).

I do not like this approach, because this list can possibly be incomplete for some concrete apps. For example, some gem can monkey patch Object with some popular name and with this approach this name now will be dangerous.

Another reason, this approach (besides properties) also makes methods with arguments as dangerous. But this is not needed, because when the user will pass arguments, then this will blow up, showing that he is doing something wrong.

So I propose to add a small explicit list of the most likely used dangerous methods. I did not add __send__/send/method_missing/etc (as mentioned in #45879 (comment)), because they require arguments and this will already blow up and won't go unnoticed.

cc @byroot