Markdown linter (#5494)

* linter

* Add markdown linter

* add env

* only check markdown

* Add token

* Update .github/workflows/test-suite.yml

* Markdown linter

* Exit code

* Update script

* rename

* mdlint

* Add an empty line after end of file

* Testing disable

* add text

* update mdlint.sh

* ori validator inclusion

* Add config yml file

* Remove MD041 and fix advanced-datadir file

* FIx validator inclusion file conflict

* Merge branch 'unstable' into markdown-linter

* change files

* Merge branch 'markdown-linter' of https://github.com/chong-he/lighthouse into markdown-linter

* mdlint

* Remove MD025

* Remove MD036

* Remove MD045

* Removr MD001

* Set MD028 to false

* Remove MD024

* Remove MD055

* Remove MD029

* Remove MD040

* Set MD040 to false

* Set MD033 to false

* Set MD013 to false

* Rearrange yml file

* Update mdlint.sh and test

* Test remove fix

* Test with fix

* Test with space

* Fix summary indentation

* Test mdlint.sh

* Update mdlint.sh

* Test

* Update

* Test fix

* Test again

* Fix

* merge into check-code

* Update scripts/mdlint.sh

Co-authored-by: Mac L <mjladson@pm.me>

* Update scripts/mdlint.sh

Co-authored-by: Mac L <mjladson@pm.me>

* Remove set -e

* Add comment

* Merge pull request #7 from chong-he/unstable

Merge unstable to markdown branch

* mdlint

* Merge branch 'unstable' into markdown-linter

* mdlint

book/src/database-migrations.md

@@ -53,13 +53,13 @@ To apply a downgrade you need to use the `lighthouse db migrate` command with th
 5. After stopping the beacon node, run the migrate command with the `--to` parameter set to the
    schema version you would like to downgrade to.
 
-```
+```bash
 sudo -u "$LH_USER" lighthouse db migrate --to "$VERSION" --datadir "$LH_DATADIR" --network "$NET"
 ```
 
 For example if you want to downgrade to Lighthouse v4.0.1 from v4.2.0 and you followed Somer Esat's guide, you would run:
 
-```
+```bash
 sudo -u lighthousebeacon lighthouse db migrate --to 16 --datadir /var/lib/lighthouse --network mainnet
 ```
 
@@ -113,7 +113,7 @@ The `schema_version` key indicates that this database is using schema version 16
 
 Alternatively, you can check the schema version with the `lighthouse db` command.
 
-```
+```bash
 sudo -u lighthousebeacon lighthouse db version --datadir /var/lib/lighthouse --network mainnet
 ```
 
@@ -132,25 +132,27 @@ Several conditions need to be met in order to run `lighthouse db`:
 
 The general form for a `lighthouse db` command is:
 
-```
+```bash
 sudo -u "$LH_USER" lighthouse db version --datadir "$LH_DATADIR" --network "$NET"
 ```
 
 If you followed Somer Esat's guide for mainnet:
 
-```
+```bash
 sudo systemctl stop lighthousebeacon
 ```
-```
+
+```bash
 sudo -u lighthousebeacon lighthouse db version --datadir /var/lib/lighthouse --network mainnet
 ```
 
 If you followed the CoinCashew guide for mainnet:
 
-```
+```bash
 sudo systemctl stop beacon-chain
 ```
-```
+
+```bash
 lighthouse db version --network mainnet
 ```
 
@@ -178,7 +180,7 @@ Here are the steps to prune historic states:
 
    If pruning is available, Lighthouse will log:
 
-   ```
+   ```text
    INFO Ready to prune states
    WARN Pruning states is irreversible
    WARN Re-run this command with --confirm to commit to state deletion
@@ -193,10 +195,10 @@ Here are the steps to prune historic states:
 
    The `--confirm` flag ensures that you are aware the action is irreversible, and historic states will be permanently removed. Lighthouse will log:
 
-   ```
+   ```text
    INFO Historic states pruned successfully
    ```
-   
+
 4. After successfully pruning the historic states, you can restart the Lighthouse beacon node:
 
    ```bash