Feature/new release flow

[hakuturu583]

Description

Abstract

• Update Pull Request template.
• Added github actions needed for the new release flow.
• Immediately after this Pull Request is merged, the version will be version 1.0.0.

Background

The development team will require stricter version control in the future to ensure backward compatibility of the traffic_simulator API.
Accordingly, releases will be automated from now on, and will be done by labeling and instructing Pull Requests.

Details

After applying the new release flow, you can put one of the labels bump major, bump minor, or bump patch on the Pull Request, and when the Pull Request is merged with master, the version of scenario_simulator_v2 is bumped according to the label type.

The commit history after applying the new release flow is shown in the figure below.

In the new release flow, the master tracking confirmation of branches using merge queue and the determination of the executability of release actions will be added.

Inside the merge queue, the release action is only judged as executable, and the actual release work is executed on the master branch after merge.

GitHub Actions for release are controlled in parallel to avoid data conflicts.

Destructive Changes

This Pull Request only adds the GitHub Actions, templates, etc. necessary for the release, and there are no disruptive changes with respect to the C++ API, scenario format, etc.

However, the existing release flow will be fundamentally changed and semantic versions will not be compatible.

[github-actions]

Checklist for reviewers ☑️

All references to "You" in the following text refer to the code reviewer.

• Is this pull request written in a way that is easy to read from a third-party perspective?
• Is there sufficient information (background, purpose, specification, algorithm description, list of disruptive changes, and migration guide) in the description of this pull request?
• If this pull request contains a destructive change, does this pull request contain the migration guide?
• Labels of this pull request are valid?
• All unit tests/integration tests are included in this pull request? If you think adding test cases is unnecessary, please describe why and cross out this line.
  • Well tested in https://github.com/merge-queue-testing/scenario_simulator_v2
• The documentation is enough? If you think adding documents for this pull request, is unnecessary, please describe why and cross out this line.