Migrate languages to use talon list files

[Nova38]

The issue #1597 seaks to simplify the implementation of of th code operators if I read it correctly. Currently it looks like a lot of list talon list are defined In their <language>.py files instead of in .tslonlist files. Would it be advantages to move those list to standardized list files inside of the given language folders instead of having them all in the .py files? It think it might be for a few reasons:

1. It could be easier to have a generic folder template for implementing a new language, and what list need to be created for it
2. If end users modify the .talonlist files I their forkss of the repo it would be easier for them to maintain their changes in separate list files instead of potentially dealing with multiple merge conflicts inside of the .py file
3. It could also help to see from a high level perspective if any languages need additional work implementing the generic tlaontwga for the given languages

[nriley]

We discussed this in the community backlog session and the short answer is that we are already migrating to .talon-list files as much as we can in community’s programming language support, for example with operators in #1650.

With respect to your first point, because languages vary so much in what operators, functions, control constructs and so forth they support, I don't think there really is such a thing as a generic language or list of lists. One way forward might be a single Python file that becomes a template of all possible language constructs that can be implemented with examples of each.

Will leave this open in case you have some specific suggestions for next steps after reviewing #1650 — thanks!