ci: test all the quickstart documents

[seeflood]

What this PR does:

• Test all the quickstart documents.
• Fix all the test failure
• Make the test script less intrusive so that we don't have to modify the documents to meet the standard

I wrote a tool mdx to make it easier to write runnable markdown files.

Ignore list:

• We will not test apollo quickstart demo because the github workflow cannot connect to the apollo server :(
  I don't know why. Maybe it's caused by that wall
  

Todo:
- [x] modify the pr title checker so that it won't warn every time

• test configuration API demo
• make the test faster and only build layotto once
• wait for fix: dubbo demo fails (#458) #459 , Use in-memory component to implement the Actuator API #463 and bug(actuator): apollo health status "INIT",even if no apollo component configurated #462 being fixed
• add a workflow to run dubbo-go example in go 1.17
• improve document
• pass all the tests
• don't remove all containers when running tests locally

Which issue(s) this PR fixes:

Fixes #447

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

[codecov]

Codecov Report

Merging #456 (c542988) into main (94a6b97) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #456   +/-   ##
=======================================
  Coverage   60.70%   60.70%           
=======================================
  Files         120      120           
  Lines        6382     6382           
=======================================
  Hits         3874     3874           
  Misses       2139     2139           
  Partials      369      369           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f7300c2...c542988. Read the comment docs.

[seeflood]

@Xunzhuo Please help review this PR. Layotto CI will test all the quickstart documentation.
I hate shell scripts. It wasted me too much time fixing the weird errors 😢
If I had another chance , I will write this tool in golang, java ,nodejs , python or any other programming language instead of shell !

[Xunzhuo]

LGTM, thanks @seeflood, we should not let core team spend more time on these infrastructure tasks anymore, let us move on:) Core abilities for new CI in Layotto have already been strong enough for now at least, we could label a good first issue on other related tasks.

[seeflood]

LGTM, thanks @seeflood, we should not let core team spend more time on these infrastructure tasks anymore, let us move on:) Core abilities for new CI in Layotto have already been strong enough for now at least, we could label a good first issue on other related tasks.

Agreed!