Fixed python 3 incompatibility in logging API implemenation of findCaller (v3.3 cherry pick)

[nmaludy]

Closes #5057

See that issue for description of what the problem was. The fix was simply to ensure our implementation handles both the python 2 version and returns a 3-tuple, along with the python 3 version which returns a 4-tuple and is based on the code here: https://github.com/python/cpython/blob/3.9/Lib/logging/__init__.py#L1502-L1536

I've tested this change both my a python 2.7 (centos7) and python 3.6 (centos8 and ubuntu18) box and the logging modules are returned properly.

[cognifloyd]

Suggested change

	https://github.com/python/cpython/blob/3.9/Lib/logging/__init__.py#L1376-L1404
	https://github.com/python/cpython/blob/3.9/Lib/logging/__init__.py#L1502-L1536

[amanda11]

I installed the package from this PR onto U18 and it did get rid of most of the unknown file messages in the logs. I'm still left with "unknown file" on exception in the st2sensorcontainer log:

2020-10-15 08:22:43,653 139699041297216 ERROR (unknown file) [-] File "/opt/stackstorm/packs/openstack/sensors/messaging_sensor.py", line 52, in poll

[nmaludy]

@amanda11 can you confirm if that is a new problem or one that already exists in 3.2?

[amanda11]

@amanda11 can you confirm if that is a new problem or one that already exists in 3.2?

I think it probably exists on 3.2 as 3.2 had lots of "unknown file" messages, but I'll confirm - I have to break a system to get the exception!

[amanda11]

@amanda11 can you confirm if that is a new problem or one that already exists in 3.2?

@nmaludy - confirmed it is python 3 only. I can raise an issue for it - it just seems to be the exceptions that are a problem now on 3.3.

[amanda11]

LGTM - I willl raise a separate issue for the "unknown module" on exceptions in sensor container on py3 (if one already doesn't exist), after confirming that the problem also exists on 3.2.

[cognifloyd]

LGTM