fixup: EBNF for documentation

Summarize the changes

• fixup: EBNF for documentation

Ensure that

• New code is covered by unit and integration tests.
• Related issues would be automatically closed with gitlab's closing pattern (Closes #issue_number).
• Public modules are documented (check the rendered version with cargo doc --open).
• (if PEST grammar has changed) EBNF grammar reflects these changes (check the result with railroad diagram generator.

Next steps

• Cherry-pick to: none / 24.X
• Update sbroad submodule in picodata/picodata.
• (if EBNF grammar has changed) create a follow-up issue in picodata/docs.