Update versioning 1.0.5, 1.2.0, 1.2.2 -> 1.2.0, 1.2.3, 1.3.0

[sunya-ch]

There are multiple reasons to restructure the versioning.

• There are multiple urgent updates (PRs) merged to v1.2.0 after release. These updates made version > 1.2.0 left behind
• v1.2.1 introduces a major to the code to support bare-metal customization which is now on-hold task
• v1.2.0 are now used in production as a stable version.

Accordingly, I would like to

• tag release-v1.2.2
• move 1.2.2 (main) to 1.3.0
• create new branch for v1.2.3
• stable v1.0.5 -> v1.2.0
• beta v1.2.0 -> v1.2.3
• alpha v1.2.2 -> v1.3.0

When resuming the task on v1.3.0, we need to later rebase the branch v1.3.0.