Tag and release rules

[JSUYA]

In the future, I will create a tag with the below rule and create a release for each tag point according to the flutter-tizen update.
{FLUTTER_VERSION}-tizen.{MAJOR}.{MINOR}.{PATH}
Each release organizes and notices major changes. (This tagging and release is not regular.)

ex)
The tag that will be created soon is 3.27.1-tizen.1.0.0.

[JSUYA]

Current tagging policy : #607 (comment)

[JSUYA]

• When a major feature update occurs in flutter-tizen, i will update the tizen version and release. This work is currently manual, but i have plann to automate it
• In order to keep the existing policy, when the next version patch is merged, a tag with the meaning of archive is tagged to the previous commit.