Fix workflow trigger for CheckLabel.yaml

[HansRobo]

Description

Abstract

To realize a trigger that fires when label is added or removed from pull-request, you should use pull_request trigger with labeled and unlabeled types instead of label trigger.

Background

N/A

Details

N/A

References

• About label trigger
• About pull_request trigger

Destructive Changes

N/A

Known Limitations

N/A

[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. This pull request only changes the trigger of the GitHub Actions.
• The documentation for this pull request is enough? If you think adding documents for this pull request is unnecessary, please describe why and cross out this line. This pull request only changes the trigger of the GitHub Actions. No need for documentation, especially since no code differences exist

[HansRobo]

Test for labeled and unlabeled

[HansRobo]

The unlabeled type of pull_request trigger works well.

[HansRobo]

The labeled type of pull_request trigger works well.