feat(create-prs-to-update-vcs-repositories): add a workflow

[sasakisasaki]

Description

This PR adds a new feature as follows:

• Check the version of all repositories in the autoware.repos
• Check if the version of the repository is the latest
• If the version is not the latest, create a PR to update the repository to the latest version
  • This PR will be created for each repository that is not the latest version
• We can specify which updates the PR should be created for.
  • In this PR, I selected major and minor.

Related links

Semantic Versioning Discussion
Discussion in the autoware-github-actions

Tests performed (Referenced from the URL in "Related links")

Same as tests performed in this PR except following points:

• We tested the version update PRs are created in the following cases:

    0.0.1  =>  0.0.2    # If `--targets patch` is used
    1.1.1  =>  1.2.1    # If `--targets minor` is used
    2.0.9  =>  3.1.4    # If `--targets major` is used

• Also we tested the version update PR is not created if the following examples:

    main       =>  0.0.1
    v0.0.1     =>  0.0.2
    xxx-0.0.1  =>  0.0.9

To know the detail of performed tests, please see the description of this PR.

Notes for reviewers

After this PR is merged, PRs for version update will be created automatically.
Perhaps we need to adjust the cron schedule here to prevent from noisy PR creation.

Interface changes

No interface changes.

ROS Topic Changes

No ROS topic changes.

ROS Parameter Changes

No ROS parameter changes.

Effects on system behavior

New PRs will be created as the vcs repository has update with the expected format of version (e.g., 0.0.2, 0.1.2, 1.2.3).

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

• I've confirmed the contribution guidelines.
• The PR follows the pull request guidelines.

In-review checklist for the PR reviewers

The PR reviewers must check the checkboxes below before approval.

• The PR follows the pull request guidelines.
• The PR has been properly tested.
• The PR has been reviewed by the code owners.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

• There are no open discussions or they are tracked via tickets.
• The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

[sasakisasaki]

@youtalk Now this PR is ready for review 👍

[sasakisasaki]

@youtalk I believe this PR is ready for merge. Your review is appreciated.

[youtalk]

LGTM finally!