fix(ci): use opentelemetrybot to sync package-lock.json on release PRs

[pichlermarc]

Which problem is this PR solving?

• see chore: release main #1798, release-please is not updating package-lock.json with the new versions, so currently we'd need to do this manually - however release please force-pushes on each merge to main, so this is tedious.
• we currently do not use the opentelemetrybot account to create release PRs
  • link to community repo issue to get the required access to @opentelemetrybot

Short description of the changes

• uses opentelemetrybot credentials to create release PRs via release please
• adds a commit as opentelemetrybot, which syncs the package-lock.json (@opentelemetrybot has signed the CLA)

[codecov]

Codecov Report

Merging #1817 (6d90d19) into main (434cab2) will not change coverage.
The diff coverage is n/a.

❗ Current head 6d90d19 differs from pull request most recent head d07fa9c. Consider uploading reports for the commit d07fa9c to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1817   +/-   ##
=======================================
  Coverage   91.42%   91.42%           
=======================================
  Files         143      143           
  Lines        7303     7303           
  Branches     1461     1461           
=======================================
  Hits         6677     6677           
  Misses        626      626           

[david-luna]

Suggestion: if you want to speed up the process you could avoid checking out again by cleaning up the workspace just after pushing you could add the following commands

git clean -xdf
npm ci
npm run compile

[pichlermarc]

Ah, yes we'd also have to check out main though as we might be on another branch at this point in the workflow.

It's also relatively quick (about 2s) compared to the rest of the workflow so I'd opt to keep it as-is (here's an example run https://github.com/pichlermarc-sample-organization/test-release-please/actions/runs/6941681633/job/18883019651). 🙂