Make first internal Python->Go endpoint: getting tutorial status

This is to create the first "internal" endpoint, from the Python server to Go. See the full description of the associated milestone for technical aspects.

For this one I've chosen the "GET" operation for the user's tutorial status. Unlike the "POST" for tutorial status, this Python endpoint deals with a lot of things other than the tutorial. Implementing all of it would be a lot at once. That's why just moving the tutorial status portion to an internal call to the Go server makes sense.

After this, we'll have both a "side by side" and an "internal" endpoint that we can model future portions of the migration after.

Note: This task is already complete as I am writing this issue. I wanted to seed my new milestone with some progress :-) It also gives a narrative for people following along who want to help.

orblivion / desert-atlas

Make first internal Python->Go endpoint: getting tutorial status #76