fix(connect): Skip update HTTP's span name and update RpcMetadata's route instead

[chigia001]

Which problem is this PR solving?

Each framework has a different approach to updating Span's name and HTTP_ROUTE attribute. We want to delegate this to instrumentation-http for consistent's name and attribute
This PR fixes the above issue for connect

• This will partially fix issue Setting HTTP_ROUTE inconsistent accross HTTP server frameworks #1381

Short description of the changes

• Skip modifying HTTP's Span name directly in instrumentation-connect code
• Update route property of RpcMetadata

[codecov]

Codecov Report

Merging #1534 (1212769) into main (f7c4324) will decrease coverage by 0.47%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1534      +/-   ##
==========================================
- Coverage   96.13%   95.67%   -0.47%     
==========================================
  Files          14       18       +4     
  Lines         906     1087     +181     
  Branches      197      221      +24     
==========================================
+ Hits          871     1040     +169     
- Misses         35       47      +12     

Impacted Files	Coverage Δ
...try-instrumentation-connect/src/instrumentation.ts	98.76% <100.00%> (ø)

... and 3 files with indirect coverage changes

[Flarna]

please avoid forced push as it makes review harder. Just merge main into your branch to keep it up to date. Merge to main will do a squash anyway.

[chigia001]

@Flarna seem like there something wrong with last run, it fail at docker pull step.

[Flarna]

@open-telemetry/javascript-maintainers Could someone please take a look on this as connect instrumentation lacks a maintainer but I think this change is useful.

[pichlermarc]

Thanks for taking care of this - happy to see this behavior aligned with the other instrumentations 🎉