version: include python version

[HumorBaby]

Last unsolicited PR until I dig into .reload more, I PROMISE 😁

Sometimes I forget which version of python I am using 😅. Really though, this stemmed from testing issues/code across multiple versions of Python. I could quickly check the Sopel version from the bot, but not the python version it was running on. This commit simply appends the Python version to the .version response.

I don't think it shouldn't really be a security issue to show the Python version of the bot... right??

[HumorBaby]

What'r the chances of that test failing for that reason..?! 😱 (Build #1470)

[dgw]

Travis getting a connection reset by peer… that's a new one. (I kicked build 1470.1, though, so it doesn't show the error any more. Could have easily made the test pass without your force-push. 😸)

I'm torn between including this in 6.6.2 (already planned to fix a few small bugs that weren't fixed in 6.6.x yet) and waiting until 7. I don't want to start a 6.7.x branch, and I kinda think this small added feature is slightly past the intent of a patch release.

Of course it's mostly useful for testing the current version, so putting this on master and not releasing it until Sopel 7 is probably fine. That'll also give plenty of time for feedback about the alleged security risk of including the Python version. (People who think the Python version is a risk probably also think the Sopel version is a risk, so I bet they just disable this module anyway. 🤣)