chore: merge two workflows into one

[170210]

Description

This PR merges deploy_to_git and release workflows into one, as both workflows are triggered by the same situation and the release workflow should work after the deploy_to_git workflow.

The logic of the workflow will be as follows:

• If the pusher is a user, it will first check whether the shared library is the latest version.
  • If it is the latest version, it will start the release workflow.
  • If it is not the latest version, it will update the shared library and stop after creating a PR.
• If the pusher is a bot, it will start directly from the release workflow.

Types of changes

• Bug fix (changes which fixes an issue)
• New feature (changes which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• ETC (build, ci, docs, perf, refactor, style, test)

Checklist

• I followed the contributing guidelines.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• The PR title and commits are followed conventional commit form.

[loloicci]

I think this PR's target is making "pushing tag work" running only when the shared library is the latest.
And, is this workflow's logic according to this rule? Is the pusher's info needed in "if" section?

[170210]

I think this PR's target is making "pushing tag work" running only when the shared library is the latest.

I think this PR can do this.

Is the pusher's info needed in "if" section?

I don't think so.
Currently, the workflow will firstly check the pusher.

• If it is a bot, it will begin from the get package version like this sample : https://github.com/170210-private/wasmvm/actions/runs/6570532993

• If it is a user, it will check shared library version.

  • If the the shared library is the latest, the sample will like https://github.com/170210-private/wasmvm/actions/runs/6651980960
  • If it is not the latest, the sample will like https://github.com/170210-private/wasmvm/actions/runs/6570389560

[loloicci]

I think this PR can do this.

OK, then please write it in the description.

If the the shared library is the latest, the sample will like

missing url. After I look it, I will approve.

[170210]

not the missing, just because I am preparing the workflow...