[SDK Suppressions labels] Add new action to update suppressions labels

[JackTn]

add new action to update sdk-suppression label

Overview :
Add sdk-suppressions file to process sdk breaking change

Changes:

• [.github/workflows/SDK-Suppressions-Label.yaml] main action added trigger by pull request
• [.github/workflows/update-labels.yaml] add trigger to update label
• [eng/tools/package.json] dependence config for sdk-suppressions
• [eng/tools/sdk-suppressions] main code to process sdk-suppressions label base diff by pr sdk-suppression.yaml file

[openapi-pipeline-app]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ The required check named SpellCheck has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide
• ❌ The required check named Protected Files has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide

[openapi-pipeline-app]

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

[mikeharder]

Address review feedback

[raych1]

@mikeharder could you review again?

[mikeharder]

I think you want to set the label in either case, both true and false correct? Both are needed to ensure labels are removed when they no longer apply.

[JackTn]

yes, true to add and false to remove

[mikeharder]

But doesn't the if condition on line 76 mean you only call add-label-artifact when the condition is true?

[JackTn]

I understand the reason for your confusion. For instance, on line 75, the step output value is 'true' or 'false', which is not a proper boolean. It's a string. Therefore, writing if 'false' will still execute. And this is my test case JackTn#17 , can you see it？

[mikeharder]

Why do you need the if condition at all? Do you need a tri-state value ("true", "false", and undefined), where undefined means neither add nor remove the label)? If so, I recommend changing the code to be more clear.

[JackTn]

The status value should have only two cases: value exists (either true or false) or undefined. If the value exists, it indicates execution, where labels are added or removed based on true or false. If it is undefined, no operation is performed.

[JackTn]

The purpose of using an if condition is to determine whether this step needs to be executed.

[raych1]

@JackTn , can you add comment inline to explain this behavior for better readability?

[JackTn]

added

[mikeharder]

Change dependency, and verify if label artifacts should be generate for both true and false.