Blocks programs w/ variables usually convert to Python programs with "global" keyword everywhere

Because all variables in blocks are global and we preserve this when converting to TS and then to PY, we end up with a lot of "global" keywords all over the place when converting to Python.

I think this is going to be especially problematic for new users learning Python since the "global" and "nonlocal" keywords are some of the more confusing aspects of the language.

Most cases these global variables should really be converted to local variables when switching to TS or PY. This could be done fairly easily if we did a liveness analysis to determine when it's safe to make variables local.

Here's a simple blocks program that is over complicated when switching to Python:

I think this will be especially problematic for Arcade since there are more variables used there.

The issue does not name any files, tests, or entry points. Start by locating the Blocks-to-TypeScript-to-Python conversion path and determine how variable scope is currently preserved; done should mean generated Python avoids unnecessary global declarations while retaining program behavior.