Fix invocation timeout when incoming request contains "x-ms-invocation-id" header

[satvu]

Issue describing the changes in this PR

resolves #10934

Pull request checklist

IMPORTANT: Currently, changes must be backported to the in-proc branch to be included in Core Tools and non-Flex deployments.

• Backporting to the in-proc branch is not required
  • Otherwise: Link to backporting PR
• My changes do not require documentation changes
  • Otherwise: Documentation issue linked to PR
• My changes should not be added to the release notes for the next release
  • Otherwise: I've added my notes to release_notes.md
• My changes do not need to be backported to a previous version
  • Otherwise: Backport tracked by issue/PR #issue_or_pr
• My changes do not require diagnostic events changes
  • Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
• I have added all required tests (Unit tests, E2E tests)

[brettsam]

This looks good -- I'd recommend sync'ing with @jviau or @fabiocav -- I recall one of them mentioning that we may need to store the original header? I'm not sure that we do, but they would likely have more details.

[jviau]

This looks good -- I'd recommend sync'ing with @jviau or @fabiocav -- I recall one of them mentioning that we may need to store the original header? I'm not sure that we do, but they would likely have more details.

I am struggling to recall this exactly. But my guess would be something along the lines of putting the existing header into a new header, like x-ms-orig-invocation-id, so the function still has access to it, but it doesn't interfere with our system.

[fabiocav]

I'm OK with us scoping the changes to what is currently in place. If we feel there's a need for us to maintain the original header (I don't think we've been able to identify valid scenarios for that), we can introduce that in another PR. That would also lead to questions about hops across multiple Function Apps.