deps(instrumentation): Move @types/shimmer into devDependencies

[lforst]

Which problem is this PR solving?

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes getsentry/sentry-javascript#12682

Short description of the changes

Shimmer has a harmful type definition (DefinitelyTyped/DefinitelyTyped#69966) which conflicts with typings in certain situations (getsentry/sentry-javascript#12682) but in general, typings should not end up in the normal dependencies.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

No tests necessary I think.

Checklist:

• Followed the style guidelines of this project
• Unit tests have been added
• Documentation has been updated

[pichlermarc]

Thanks for opening this PR.

@types/shimmer is part of the public API (which is bad and is also blocking marking @opentelemetry/instrumentation as stable). In the current state this PR will break any user that has skipLibCheck: false.

I think what we'd have to do here is to wrap the shimmer functionality and providing our own types for it. Some details in #4837 (i just created this earlier based on this PR).

[lforst]

@pichlermarc Thanks for the heads-up! I didn't properly check whether the dependency was used. I assumed it was put there by mistake 😄

I hope the "hostile" typedef change gets merged soon: DefinitelyTyped/DefinitelyTyped#69966 which would make shimming shimmer less important.

[lforst]

Closed in favor of #4854 now that DefinitelyTyped/DefinitelyTyped#69966 was merged and released.