v0.37.x: Removing all the vuepress related build files and references (backport #253)

[mergify]

This is an automatic backport of pull request #253 done by Mergify.
Cherry-pick of d159562 has failed:

On branch mergify/bp/v0.37.x/pr-253
Your branch is up to date with 'origin/v0.37.x'.

You are currently cherry-picking commit d159562d0.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   Makefile
	deleted:    docs/.textlintrc.json
	deleted:    docs/.vuepress/styles/index.styl
	modified:   docs/architecture/README.md
	deleted:    docs/package-lock.json
	deleted:    docs/post.sh
	deleted:    docs/pre.sh
	deleted:    docs/stop-words.txt

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   RELEASES.md
	deleted by them: docs/.vuepress/config.js
	deleted by them: docs/.vuepress/redirects
	both modified:   docs/DOCS_README.md
	deleted by them: docs/package.json
	deleted by them: docs/versions

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[thanethomson]

@Mergifyio rebase

[mergify]

⚠️ This pull request got rebased on behalf of a random user of the organization.
This behavior will change on the 1st February 2023, Mergify will pick the author of the pull request instead.

To get the future behavior now, you can configure bot_account options (e.g.: bot_account: { author } or update_bot_account: { author }.

Or you can create a dedicated github account for squash and rebase operations, and use it in different bot_account options.

[mergify]

rebase

✅ Branch has been successfully rebased

[andynog]

fixed merging issues, looks good to me now.