Fix wrong service invocation type in http tracing

[RayOnFire]

Description

If request contains header dapr-app-id, this PR will treat it as a service invocation.

Issue reference

Please reference the issue this PR will close: #[7085]

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Created/updated tests
• Unit tests passing
• End-to-end tests passing
• Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
• Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
• Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

[ItalyPaleAle]

Thanks for this!

I believe when #6919 is merged, it should supersede this issue and fix this bug too. Let's get that merged first :)

[ItalyPaleAle]

Let’s wait on #6919 which should address this issue at the root.

[yaron2]

@RayOnFire if you can please pull the master branch version, build a daprd binary and see if the issue is now resolved, that would help a lot.

[daixiang0]

Suggested change

	appId := r.Header.Get("dapr-app-id")
	appID := r.Header.Get("dapr-app-id")

[ItalyPaleAle]

In the current master branch, we changed how tracing works significantly. Could you please make sure this PR is still needed?

[yaron2]

Ping @RayOnFire

[dapr-bot]

This pull request has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions!

[yaron2]

Ping @RayOnFire

[RayOnFire]

Hi, sorry for the late reply. I think in the current master branch, this PR is no longer needed. Thank you for your comment & code review!