fix(actions): ♻️ rebuild ci publish system

[yi-Xu-0100]

The release workflow will run with the follow steps by trigger manually:

1. Set up job and checkout code for all history with tags.
2. Bump version of package.json and write change log with standard-version.
3. Pretty the format of CHANGELOG.md, push the commit, and add a tag.
4. Follow the official tutorials to publish extension.
5. Build the .vsix.
6. Get the release note from the formated CHANGELOG.md by using mindsers/changelog-reader-action.
7. Create release.
8. Upload release asset.

Other changes:

1. add CHANGELOG.md into .prettierignore.
2. add the script deploy for publish.
3. delete the script version.
4. delete the script release.
5. use the cmd of sed 's/^### \[/## [/' -i CHANGELOG.md to change the changelog content, because it will make content to fit the markdown rules.
6. use the cmd of yarn prettier --write CHANGELOG.md --prose-wrap never --ignore-path ./gitignore to pretty the format of CHANGELOG.md, and it will make content to fill correcttly with the release body.

Close #59

[yi-Xu-0100]

@vivaxy I test in my fork repo and will also push any commit in fork repo in the future in case that I push a mistake to commit.

I also add the tag in the steps, it works well except for the publishing which I can not test. See in https://github.com/yi-Xu-0100/vscode-conventional-commits/releases/tag/v1.17.0

If there are no more suggestions for the steps, I will squash and merge the PR and will test to publish a patch version. 😀

[vivaxy]

Awesome! I have no more questions.