fix(connect): fix wrong rpcMetada.route value not handle nested route

[chigia001]

Which problem is this PR solving?

• connect allow having nested connect instance, which can be used to setup nested route. When using this setup, the current instrumentation code will alway override with the sub-route and not take into account the route of parent connect instance
• This is discover when implement fix(connect): Skip update HTTP's span name and update RpcMetadata's route instead #1534 (discusion)
• Also need to take into the account of trailing splash in route middlewere when construct nested route. See Express instrumentation does not normalize paths (removing double slashes) #1547

Short description of the changes

• Need another layer of patching for connect's handle method. Whenever handle is call, we add another layer in the stack. If handle also call with an out method, we must pop the stack before out is execute. (this is opposite with current patched next where we call next first before finish span)
• On route's middlewere, each time connect call the route's handle, update the latest value in the stack with middlewere's route value, use current stack value to calculate current rpcMetadata.route value.
• This setup allow capture the last route middlewere executed with correct nested app.

[codecov]

Codecov Report

Merging #1555 (db31f3e) into main (8802eae) will increase coverage by 0.04%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1555      +/-   ##
==========================================
+ Coverage   91.75%   91.80%   +0.04%     
==========================================
  Files         137      139       +2     
  Lines        7084     7124      +40     
  Branches     1426     1432       +6     
==========================================
+ Hits         6500     6540      +40     
  Misses        584      584              

Files Changed	Coverage Δ
...try-instrumentation-connect/src/instrumentation.ts	99.01% <100.00%> (+0.25%)	⬆️
...etry-instrumentation-connect/src/internal-types.ts	100.00% <100.00%> (ø)
...opentelemetry-instrumentation-connect/src/utils.ts	100.00% <100.00%> (ø)

[pichlermarc]

Broken CI will be fixed once #1556 is merged, sorry for the inconvenice. 😞

[chigia001]

I think this PR also have some GH action's cache issue like my PR for express. Not sure how we can resolve those issue.

[chigia001]

can we merge this or add pkg:instrumentation-connect label so we can test tav for this?

[blumamir]

LGTM. Apologies for the long time to review, and thank you for all the great contributions.

I added a few nit comments which are all optional and do not block. Feel free to resolve them if you don't want to spend more time on this PR (or address them if you are in the mood).

[blumamir]

LGTM.

Thanks for addressing the comments 🙏 and for these contributions.

Please fix the lint so I can merge

[chigia001]

@blumamir fixed