fix: change span names for socket-io

[povilasv]

Which problem is this PR solving?

Socket io span names might contain high cardinality data. I'm removing roomId from span names so it doesn't.

Issue: #1937

Short description of the changes

• I refactored names so It follows messaging semconv, it's "send ${namespace}" / "receive ${namespace}" instead of ... receive.

One question about should it be "receive", I think we might need to change it to "process"?

Given:

“Receive” spans SHOULD be created for operations of passing messages to the application when those operations are initiated by the application code (pull-based scenarios).

“Process” spans SHOULD be created for operations of passing messages to the application when those operations are not initiated by the application code (push-based scenarios). Such “Process” span covers the duration of such an operation, which is usually a callback or handler.

Ref: https://opentelemetry.io/docs/specs/semconv/messaging/messaging-spans/#consumer-spans

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.88%. Comparing base (30e8fc5) to head (05712c6).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2495   +/-   ##
=======================================
  Coverage   90.88%   90.88%           
=======================================
  Files         159      159           
  Lines        7844     7844           
  Branches     1616     1616           
=======================================
  Hits         7129     7129           
  Misses        715      715           

[blumamir]

LGTM, the room should not be part of the span name and the operation should be first according to the span name of messaging spans.

Thanks for fixing it.

[blumamir]

@povilasv please fix the lint error with npm run lint so CI is green

[povilasv]

@blumamir fixed, thanks!