PythonSession should always set recording-id when acquiring global session

[jleibs]

Full discussion here:
#1778 (comment)

TLDR:

• We currently initialize the RecordingId during python init.
• Until python init has been run, the RecordingId is left with a value of ZERO
• It is conceivable (though practically difficult) to end up in a situation where some message is send using this RecordingId
  • Note: I don't believe this is actually possible in pure python code, but could show up in an edge case of another rust-based python extension logging something during init.

I think the right solution is to change python_session() to take the Python<_> object as an argument, which would then allow us to always initialize the session correctly. However, this requires some case since it introduces new potential for deadlocks, in particular the kinds of problems resolved in: #843