chore: add workflow for surveys of non-members

[maryliag]

The Contributor Experience group created a survey to help understand challenges and feedback from new contributors. We have this survey running for a few months on opentelemetry.io and the JS repo, with helpful feedback, so now adding to more repos.

Example of message: open-telemetry/opentelemetry-js#5884 (comment)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.01%. Comparing base (7ef1410) to head (3e2f302).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #7640      +/-   ##
============================================
- Coverage     90.01%   90.01%   -0.01%     
+ Complexity     7091     7090       -1     
============================================
  Files           803      803              
  Lines         21443    21443              
  Branches       2092     2092              
============================================
- Hits          19302    19301       -1     
  Misses         1477     1477              
- Partials        664      665       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[breedx-splk]

Is there a distinction here between closed and merged? I forget...but might it create a weird experience if a closed PR offers the same survey and claims it was merged?

[maryliag]

there is no distinction on the type here, but this is to trigger the event, and a few lines below (line 21) there is a check if: github.event.pull_request.merged == true before adding the comment, so it shouldn't comment if is just closed

[breedx-splk]

This stuff is magic and I love it.

[trask]

oh no, I've been trying to get rid of opentelemetrybot 😄 open-telemetry/community#2863

can you use the new otelbot app, and same as you roll this out to other repos?

[maryliag]

to confirm, is just replacing with steps.otelbot-token.outputs.token and should be available for all repos, or is there something I need to do to have it available on the repos I'm adding this survey?

I'm adding to:

• collector, which looks like is ready to use
• .NET, which doesn't seem to be ready to use according to this

This survey already exists like this in:

• JS repo, no idea if it can be updated
• opentelemetry.io, which doesn't look like I can update according to the same comment as the .NET one

[otelbot]

Thank you for your contribution @maryliag! 🎉 We would like to hear from you about your experience contributing to OpenTelemetry by taking a few minutes to fill out this survey.

[trask]

Oops looks like I broke it, will investigate 🙈

[trask]

open-telemetry/community#2971

[trask]

looks like that fixed it: open-telemetry/opentelemetry-java-instrumentation#14600

[trask]

though I'm now confused, because I only just now "accepted" the permission update to otelbot (forgot there was a second step) 🤔

[maryliag]

looks like that permission was not required for all the prior use cases? will keep an eye if this will continue working as expected now

[trask]

same, I'll copy you if I see anything unusual this week