Enable call stack logging for deprecation warnings (optional)

[Badiboy]

Description

I found that for some deprecations I cannot find where it happens to fix it.

2024-10-20 14:41:27,885 (types.py:9267 Thread-12442 (process_request_thread)) WARNING - TeleBot: "Deprecation warning: the filed "from_user" is not accessible for InaccessibleMessage. You should check if your object is Message instance before access."
2024-10-20 14:41:27,885 (types.py:9267 Thread-12442 (process_request_thread)) WARNING - TeleBot: "Deprecation warning: the filed "from_user" is not accessible for InaccessibleMessage. You should check if your object is Message instance before access."
2024-10-20 14:42:31,599 (types.py:9267 Thread-13476 (process_request_thread)) WARNING - TeleBot: "Deprecation warning: the filed "from_user" is not accessible for InaccessibleMessage. You should check if your object is Message instance before access."
2024-10-20 14:42:31,599 (types.py:9267 Thread-13476 (process_request_thread)) WARNING - TeleBot: "Deprecation warning: the filed "from_user" is not accessible for InaccessibleMessage. You should check if your object is Message instance before access."

Thus I propose to add an option that will enable call stack logging for deprecations, so developer can find the reason.

[coder2020official]

I'm sure there is a better way of implementing this, but I can't take a look at this issue right now

[Badiboy]

I'm not in a hurry with this. Please, take a look when you will have time.
If you have better idea - let me know )

[Badiboy]

@coder2020official I'm not in a hurry, but I really need this in reasonable time )

[coder2020official]

Hi, I couldn't really come up with a far better implementation, but at least I propose doing this:

• creating a function called log_deprecation_warning, which will accept a string warning and return nothing; inside, it will output warning, check for constant value, and if needed, output another warning.

[Badiboy]

@coder2020official refactored.