chore: add a few packages to release config

[Flarna]

Which problem is this PR solving?

Release please doesn't release all packages.

Refs: #871

Short description of the changes

Added opentelemetry-propagation-utils, opentelemetry-instrumentation-fastify and opentelemetry-instrumentation-long-task to release config.

Checklist

• Ran npm run test-all-versions for the edited package(s) on the latest commit if applicable.

[blumamir]

Thanks!

[codecov]

Codecov Report

Merging #873 (59ebb04) into main (ecd0307) will not change coverage.
The diff coverage is n/a.

❗ Current head 59ebb04 differs from pull request most recent head 080edb9. Consider uploading reports for the commit 080edb9 to get more accurate results

@@           Coverage Diff           @@
##             main     #873   +/-   ##
=======================================
  Coverage   95.29%   95.29%           
=======================================
  Files          10       10           
  Lines         701      701           
  Branches      142      142           
=======================================
  Hits          668      668           
  Misses         33       33           

[Flarna]

It seems adding a package to release config doesn't trigger a release.
Looking into #871 it's maybe a good idea to trigger a release manually. Or do we need a dummy commit in fastify instrumentation to get this done?

[dyladan]

I think you actually need to add them to the manifest https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/.release-please-manifest.json

[dyladan]

There are 2 files for some reason. The manifest tracks the currently released versions and the config tracks where the packages exist in the directory tree

[Flarna]

Hmm, I was doing the same as #840 did for tedious which was finally included by #815 and tedious was added in .release-please-manifest by the release main PR.