Add release action

[ddoktorski]

Closes #3

Test run in my fork repository

[ddoktorski]

Note: It looks that running taiki-e/create-gh-release always creates a release tag from the default branch, as it uses gh release create, here is the exact line. The only exception occurs if the tag for the intended release already exists. The point is that I decided to add this check to prevent a situation where running this workflow on a branch other than main would build assets from this branch but create a release tag from the latest commit on the main branch. While this introduces some limitations, I think it's better to have this explicitly highlighted here.