ci: add sync-beta-upstream

[shmpwk]

Description

This workflow is intended for the use in the repositories created by forking tier4/autoware_launch.
It means this PR does not work in tier4/autoware_launch.

• A beta branch in forking repository synchronizes with a beta branch in tier4/autoware_launch.
  • We need to set base-branch: beta/<version> and sync-target-branch: beta/<version> such as base-branch: beta/v3.0.0 and sync-target-branch: beta/v0.29.0 in each product.
• Triggerd every 5 a.m.

Backgound

Currently, in our product release test, we only develop our own product such as xx1.
But those commits should be given back to the vanilla pilot-auto and should be shared with the other products.
Here, we propose to create rule: In product development, commit vanilla pilot-auto first and then syncronize with each product.
We need to develop sync CI to syncronize our product with pilot-auto and autoware_launch. This PR is the one for it.

Related links

INTERNAL_LINK

Tests performed

We have a similar CI: https://github.com/tier4/autoware_launch/blob/tier4/main/.github/workflows/sync-tier4-upstream.yaml
It is commonly used and I believe it can replace our test.

Notes for reviewers

Effects on system behavior

• For each product, please change base-branch: beta/<version> and sync-target-branch: beta/<version> such as base-branch: beta/v3.0.0 and sync-target-branch: beta/v0.29.0.
• We need to manually change the version everytime the new product release starts.

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.

[dkoldaev]

Thank you for the PR! Can you explain with an example of what is the proposed process and how the PR will work in it. As I understood, all products will be forked from vanilla and will be getting updates from vanilla. But the addition is that all products will also be giving back their updates to the vanilla version. Is my understanding of your idea correct?

[shmpwk]

@dkoldaev
Thank you for your comment, and yes it is as I said in the slack.

各リファレンスデザインは、tier4/autoware_launch からsyncした変更をtier4/autoware_launch.* に入れる。
パラメタの変更はtier4/autoware_launch.* に入れる
パラメタ以外の変更はtier4/autoware_launch に入れてから、tier4/autoware_launch.*にsyncする。