feature(md2pdf): automatically convert md files to pdf files and release packages

[jwb528]

This feature will convert all markdown files in /docs{LinuxCommand, LinuxTool} to pdf files and save the pdf files in /pdfs every day.

This feature will release a package of pdf files everyday.

Resolves #22

Work shedule:

• [x] Find similar repo: https://github.com/wshuyi/demo-batch-markdown-to-pdf. This repo provides a tex file (for formatting) and some arguments for using pandoc to convert mds to pdfs

• [x] Learn how to commit and push changes on a workflow: https://github.com/ad-m/github-push-action

• [x] Finish the step for configure environment for md2pdf: totally pandoc and xelatex. Just need to install pandoc and TinyTex and then add them to the PATH (and this bothered me for quite long).

• [x] Test the workflow on one markdown file. Here is the run: pandoc 1.md -o 1.pdf --pdf-engine=xelatex -V mainfont='PingFang SC' --template=template.tex

• [x] Finish and test the workflow on this repo. Just traverse the md files in this repo and apply the stragedy

• [ ] Fix the bugs concerning converting images and rarely-used symbol

• [ ] Learn how to release packages in a workflow

• [ ] Finish the workflow concerning auto-releases

[mergify[bot]]

Thanks for opening this pull request! Please check out the contributing guidelines in README.md.

[mergify[bot]]

@jwb528 Contribution Message Convention Tests failed with GitMagic. Please check details or README.md for more information.

[mergify[bot]]

@jwb528 Wrong PR Title: feature: automatically convert md files to pdf files and release a package Please check README for more information.

[mergify[bot]]

@jwb528 Contribution Message Convention Tests failed with GitMagic. Please check details or README for more information.

[mergify[bot]]

All checks passed. Please wait for review.

[mergify[bot]]

All checks passed. Please wait for review.

[mergify[bot]]

All checks passed. Please wait for review.

[BobAnkh]

对于commit记录，我目前有一些新的建议（本次无需修改，后续希望注意），因为最近在开发一个新的action，关于使用conventional commit message来生成changelog，所以，你对于本feature开发的各项内容的scope我认为还是应当都写成一致的md2pdf，便于changelog生成的一致性，可能模块名称（功能名称）更为简洁直观，具体修改的文件可以在body部分体现出来。

另外，鉴于你目前该分支上奇怪的commit越来越多了，建议将部分commit使用rebase来进行适当合并，以保持整洁性，而无需过度在意每次仅针对一个文件进行修改。如有把握不准，也可以在此询问

[jwb528]

对于commit记录，我目前有一些新的建议（本次无需修改，后续希望注意），因为最近在开发一个新的action，关于使用conventional commit message来生成changelog，所以，你对于本feature开发的各项内容的scope我认为还是应当都写成一致的md2pdf，便于changelog生成的一致性，可能模块名称（功能名称）更为简洁直观，具体修改的文件可以在body部分体现出来。

另外，鉴于你目前该分支上奇怪的commit越来越多了，建议将部分commit使用rebase来进行适当合并，以保持整洁性，而无需过度在意每次仅针对一个文件进行修改。如有把握不准，也可以在此询问

了解