Deprecate instrumentation scope processor

[EdwardJXLi]

Description

Deprecate the existing modifyscope processor within ops-agent and migrate to utilizing the transform processor OTTL for achieving the same functionality.

Related issue

N/A

How has this been tested?

Unit Tests & Integration Tests

Checklist:

• Unit tests
  • Unit tests do not apply.
  • Unit tests have been added/modified and passed for this PR.
• Integration tests
  • Integration tests do not apply.
  • Integration tests have been added/modified and passed for this PR.
• Documentation
  • This PR introduces no user visible changes.
  • This PR introduces user visible changes and the corresponding documentation change has been made.
• Minor version bump
  • This PR introduces no new features.
  • This PR introduces new features, and there is a separate PR to bump the minor version since the last release already.
  • This PR bumps the version.

[ridwanmsharif]

failures seem like flakes. Retrying now

[franciscovalentecastro]

Why not just update the implementation of ModifyInstrumentationScope with the new use of the otel.Transform processor ?

IMO this would be helpful in the long run to reduce code duplication, reduce tech debt and the overall maintenance of 3P app receiver implementations. Also, it will identify this processor instance for future readers with purpose of "changing the instrumentation scope".

[EdwardJXLi]

cc @ridwanmsharif @avilevy18, I think we discussed this and the idea was deprecating ModifyInstrumentationScope entirely would decrease the surface area of otel.processors, since ModifyInstrumentationScope and Transform are almost identical anyways

[EdwardJXLi]

Heads up, ended up changing the strategy to use the existing otel.TransformationMetrics processor instead.

[franciscovalentecastro]

Sounds good! The new use of the existing otel.TransformationMetrics to set Scope looks good to me.

[ridwanmsharif]

This is a great reduction of tech debt. Thanks for this!