feat(markdown): support markdown grammar code generation

[suxin2017]

Summary

grammer support
support commonmark grammer defined

Test Plan

add quick test

[codspeed-hq]

CodSpeed Performance Report

Merging #3775 will degrade performances by 6.57%

_{Comparing suxin2017:feature_markdown_parser (4682d04) with main (1599555)}

Summary

❌ 1 regressions
✅ 106 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	main	suxin2017:feature_markdown_parser	Change
❌	router_17129688031671448157.ts[uncached]	2.4 ms	2.5 ms	-6.57%

[ematipico]

@suxin2017

I'm not sure what's your plan, but if your plan is to ship everything with one PR, please refrain from doing so:

• too much code to review
• too much work to do

Please consider breaking down the works in multiple PRs. Pros:

• easier to review
• work can be delegated to other contributors
• better vision of where the job is going

[suxin2017]

@suxin2017

I'm not sure what's your plan, but if your plan is to ship everything with one PR, please refrain from doing so:

• too much code to review
• too much work to do

Please consider breaking down the works in multiple PRs. Pros:

• easier to review
• work can be delegated to other contributors
• better vision of where the job is going

At this stage, the plan is like this

• markdown_parser support for building full project structure
• Supports mardkown's grammer generation

Then we start parsing the syntax

• Support for block parsing
  -...
• Supports inline parsing
  -...
• Support for extended parsing
  -...

At present, the first two have been basically completed, so I will first modify this pr to achieve the first two goals. In the subsequent work, I will create an issue for subdivision, and then associate it through multiple pr. Is that OK

[suxin2017]

Can someone review it for me? @ematipico @Conaclos

[dyc3]

nit: consider maybe using the prefix Md instead of Markdown for these syntax nodes?

[suxin2017]

I think it's a good idea, is it ok if I change it in the next pr

[dyc3]

Sure