Add CI/CD for publish NPM after push tag or merged

[ans-4175]

To ease publish burden from maintaner. So pipeline will automate anything that merged onto master branch

[ajiagahari]

to make CI/CD more meaning, we need testing...

[yuhanasy]

Another reason is, maybe somehow we don't want to publish directly everytime we merging new feature. Maybe there must some other updates until we ready to publish the new version.
Of course, it will be solved by using tag as trigger.

But, in here I propose another way, which I think it's as simple as doing git tag and git push --tag, as in this PR #20 .