[repo] Add-labels workflow fix

[CodeBlanch]

Follow-up to #5601

Changes

• Fix the add-labels.yml workflow so that the powershell properly handles issue body text containing newlines (see: https://github.com/open-telemetry/opentelemetry-dotnet/actions/runs/9033019307/job/24822395367)

Merge requirement checklist

• CONTRIBUTING guidelines followed (license requirements, nullable enabled, static analysis, etc.)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.74%. Comparing base (6250307) to head (833337b).
Report is 216 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5605      +/-   ##
==========================================
+ Coverage   83.38%   85.74%   +2.35%     
==========================================
  Files         297      254      -43     
  Lines       12531    10985    -1546     
==========================================
- Hits        10449     9419    -1030     
+ Misses       2082     1566     -516     

Flag	Coverage Δ
unittests	?
unittests-Solution-Experimental	85.72% <ø> (?)
unittests-Solution-Stable	85.40% <ø> (?)
unittests-Unstable-Core	19.85% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 112 files with indirect coverage changes

[reyang]

Would this be a script injection concern? For example if the user put something like "@ in the issue description? This bring a general concern regarding how are script injection are handled in other CI flows.

[CodeBlanch]

Yikes ya you are right. I updated it so it doesn't inject anything into the script content.

[CodeBlanch]

Just thinking, should we make a dropdown for "signal" (tracing/logs/metrics/other?) on the bug template and also add a label for that?

[reyang]

Just thinking, should we make a dropdown for "signal" (tracing/logs/metrics/other?) on the bug template and also add a label for that?

I guess this would be useful to the user for the feature request template, maybe start from there and see how things work, and if went well, come back to the bug template.