refactor(generators): Introduce LuaGenerator class, Order enum

[cpcallen]

The basics

• I branched from develop
• My pull request is against develop
• My code follows the style guide
• I ran npm run format and npm run lint

The details

Resolves

Part of #7085.

Proposed Changes

Introduce a LuaGenerator class to be the class of which luaGenerator is an instance (without any additional properties making it a singleton).
Introduce an Order enum (for now Closure-style) for the operator precedence table.
Don't rename luaGenerator to Lua in generators/lua/*.js.

Behaviour Before/After Change

There should be no changes in behaviour.

Reason for Changes

See #7085.

Test Coverage

Passes npm test; no changes to manual testing anticipated.

Documentation

Documentation for the LuaGenerator class and Order enum should be automatically generated by our JSDoc configs.

Additional Information

It is now possible to create multiple luaGenerator objects, which can share (or not share) block generator implementations. Note that new instances do not by default come with any generator functions pre-installed.

import{luaGenerator,LuaGenerator}from'blockly/lua';constcustomJSGenerator=newLuaGenerator();// Optionally copy standard generator functions to new instance:Object.assign(customLuaGenerator.forBlock,luaGenerator.forBlock);// Optionally add/replace some/all generator functions:customLuaGenerator.forBlock('block_type')=function(block){/* new implementation */};// Optionally change settings:customLuaGenerator.INDENT='\t';// Use tabs to indent generated code.

We now provide an enum of the operator precedence values (order of operations) constants as a separate export:

import{luaGenerator,Order}from'blockly/lua';// Old:luaGenerator.forBlock('answer_expression_block')=function(block){constcode='42';return[code,luaGenerator.ORDER_ATOMIC]}// New:luaGenerator.forBlock('answer_expression_block')=function(block){constcode='42';return[code,Order.ATOMIC]}

DEPRECATION: The .ORDER_* constants on luaGenerator are deprecated; they still exist but are no longer part of the documented API and will be removed in a future version of Blockly. We recommend that you update your custom generator code to use the Order enum at your earliest convenience.

[maribethb]

LGTM, but similar to the JavaScript change, and for the other generators, please tag the PR with deprecation and add info to the PR description about the changes to Order for developers to read.

[cpcallen]

…please tag the PR with deprecation and add info to the PR description about the changes to Order for developers to read.

I've added an "Additional Information" section with prominent DEPRECATION: notice to each of the five LangGenerator PRs.