Update to Peggy v3.0.1

• Update to Peggy v3.0.1
• Handle character escapes
• Rule names can include _ or $
• De-bounce parsing, to deal with multiple changes in a row
• Make proxy rules work by not applying pass-through transform
• Syntax errors now get underlined
• Update GitHub Actions to latest versions

Update to peggy 2.0.1

• #23: Upgraded to peggy 2.0.1, from @hildjj
  • Can show multiple errors instead of just the first
  • Can show warnings
  • Prefs for controlling debug console output (default: false) and info-level messages (default: true)
• #22: Add inline syntax highlighting in JavaScript template string, from @sanket143

Update to peggy 1.2

Support GrammarError.diagnostics, allowing tracing errors to their root causes.

Bug fix

Fixes #11: Code functions do not work when identifier contains number

Add symbols for intializers

Add symbols {Per-parse initializer} and {{Global initializer}} if the respective initializer exists.

Semantic features

Added the following features, inspired by vscode-pegjs:

• Go to / Peek Definition: Right-click a rule name, and go to its definition.
• Go to / Peek References: Right click a rule name, and see all of the places it is used.
• Rename Symbol: Rename a rule and all of the places that it is used.
• Outline / Symbol Support: See the current rule in the breadcrumbs at the top of the editor, and a list
  of all of the rules in the Outline view.

Since we were already using an embedded language server, all of the vscode-pegjs code needed to be rewritten anyway, rather than included as-is. The approach taken was to use the AST created by the Peggy parse of your grammar before code generation to extract semantics from your code every time it changes.