feat(op): Add handler op

[msonnb]

Description

Add handler op to the web_server category for spans that instrument http request handlers in server frameworks like express, fastify, etc.

PR Checklist

• I have run yarn test and verified that the tests pass.
• I have run yarn generate to generate and format code and docs.

If an attribute was added:

• The attribute is in a namespace (e.g. nextjs.function_id, not function_id)
• I have used the correct value for apply_scrubbing (i.e. manual or auto. Use never only for values that should never be scrubbed such as IDs)

If an attribute was deprecated:

• I've followed the policies described in CONTRIBUTING.md

[github-actions]

Semver Impact of This PR

🟡 Minor (new features)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

New Features ✨

Op

• Add handler op by msonnb in #554

• Add router span operation by msonnb in #551

Internal Changes 🔧

Deps

• Bump dompurify from 3.4.12 to 3.4.13 by dependabot in #559
• Bump js-yaml from 4.3.0 to 4.3.1 by dependabot in #560

Other

• Unstale yarn.lock by Lms24 in #561

---

_{🤖 This preview updates automatically when you update the PR.}

[Lms24]

Let's do handler instead please after discussing this with @cleptric. Thanks!

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit cafc13a. Configure here.}

[Lms24]

Thanks! I think we'll also need description and name rules for this op. I think we can use the following templates for these spans from checking the use cases in the SDK:

Description:

1. {http.route}
2. {url.path}

Name:

1. {http.route}
2. "Request handler

Does that sound reasonable to you?

[msonnb]

sound reasonable yes! added in f23927c

[Lms24]

thanks!