Mark two-segment CamelCase code identifiers as JUNK - Fix #4736

[alexmohr]

This prevents false author detections.
Words like MeterProvider, TracerProvider, and SpanProcessor in code comments match the "created by a " grammar pattern, producing false author detections. The existing CamelCase JUNK rule only catches three or more segments (e.g. GetQueueReference). This adds a targeted rule for two-segment CamelCase words ending in common code suffixes (Provider, Processor, Exporter, Handler, Factory, etc.) so they are tagged as JUNK.

Fixes #4736

Tasks

• Reviewed contribution guidelines
• PR is descriptively titled 📑 and links the original issue above 🔗
• Tests pass -- look for a green checkbox ✔️ a few minutes after opening your PR
  Run tests locally to check for errors.
• Commits are in uniquely-named feature branch and has no merge conflicts 📁
• Updated documentation pages (if applicable)
• Updated CHANGELOG.rst (if applicable)

---

Alexander Mohr alexander.m.mohr@mercedes-benz.com, Mercedes-Benz Tech Innovation GmbH
Provider Information

[alexmohr]

The errors in the pipeline seem unrelated to my changes, as the interupt tests should not be affected by the changes I made.
If this is not a pre-existing issue in the tests, please let me know and I'll take a closer look. Other PR like #4732 fail with the same reason.