Planned to release cpp-linter-action v2.0.0 (v2)

[shenxianpeng]

• Abstract python sources from cpp-linter-action to cpp-linter repo cpp-linter#1
• Update RREAME.md about what's new
• Remove publish-pypi.yml (Upload Python Package) #91
• Automaticlly retag for the new release #92
• Cleanup cpp_linter source code starting from v2 #95
• Change action from using docker to composite steps #88
• redirect install of python pkg to PyPI #98
• Rename action from "C/C++ Lint Action" to "C/C++ Linter" #97

[shenxianpeng]

I'm trying to create main branch from master branch, I noticed the tasks (fixed issues and enhancements) in above description have already been merged into the master branch, but we did not release them.

So I think we should release the last v1 release (v1.5.0) from master branch, then create main branch for release v2.

I will set main as our default branch and lock master branch to prevent any changes after this release.

What are your thoughts? @2bndy5

[2bndy5]

So I think we should release the last v1 release (v1.5.0) from master branch, then create main branch for release v2.

I was kinda expecting this would happen before resuming review of #83 So I'm ok with releasing v1.5.0 and creating a new main branch.

[shenxianpeng]

All the tasks are done, and it's time to release v2.0.0 🚀