## Describe the bug
I'm using the Opentelemetry Operator with the Instrumentation CRD to instrument (get traces from) Free5GC for the registration procedure with UERANSIM. When analysing the traces obtained via Otel, i see (in Jaeger) unusual traces (with long spans of >1second) with the HTTP PRI method:

![image](https://github.com/free5gc/free5gc/assets/62351083/9241853e-c6db-4d48-925d-1891dc596df7)

These PRI traces are certainly unexpected to say the least. The HTTP PRI method "is never used by an actual client. This method will appear to be used when an HTTP/1.1 server or intermediary attempts to parse an HTTP/2 connection preface." (based on https://webconcepts.info/concepts/http-method/PRI). So i imagine this means that the HTTP requests are send between a client and a server where there is an HTTP version mismatch?

Otherwise the logs on both otel instrumentation container and the otel operator seem clean:

![image](https://github.com/free5gc/free5gc/assets/62351083/b3f2da8c-5d8f-4c9c-aa52-2f2bc5a025fa)

![image](https://github.com/free5gc/free5gc/assets/62351083/1fb087cd-cc3a-4e76-99ba-3736e72ccc43)


## To Reproduce
Steps to reproduce the behavior:
Deploy Otel Operator, Go Instrumentation, Free5GC (latest) and Jaeger. (all latest versions)
View logs from the otel sidecar container or traces in Jaeger
Observe unusual traces with HTTP PRI method in Jaeger.

## Expected behavior
The HTTP PRI method is definitely unexpected. Other than that, the F5gc works as expected - can see the registered user in the WebUI.

## Environment (please complete the following information):
OS: Ubuntu 20.04 LTS Kernel v 5.15.0-105-generic
Go Version: 1.17.8 (Free5gc)
Version: otel operator latest, same with instrumentation


### PCAP File
Not available yet. I can reproduce this issue if the PCAP is needed.

[Bugs] HTTP PRI method appearing in distributed tracing
This is a GitHub Issue
repo:free5gc
owner:free5gc
Title : [Bugs] HTTP PRI method appearing in distributed tracing
Issue date:

--- start body ---
## Describe the bug
I'm using the Opentelemetry Operator with the Instrumentation CRD to instrument (get traces from) Free5GC for the registration procedure with UERANSIM. When analysing the traces obtained via Otel, i see (in Jaeger) unusual traces (with long spans of >1second) with the HTTP PRI method:

![image](https://github.com/free5gc/free5gc/assets/62351083/9241853e-c6db-4d48-925d-1891dc596df7)

These PRI traces are certainly unexpected to say the least. The HTTP PRI method "is never used by an actual client. This method will appear to be used when an HTTP/1.1 server or intermediary attempts to parse an HTTP/2 connection preface." (based on https://webconcepts.info/concepts/http-method/PRI). So i imagine this means that the HTTP requests are send between a client and a server where there is an HTTP version mismatch?

Otherwise the logs on both otel instrumentation container and the otel operator seem clean:

![image](https://github.com/free5gc/free5gc/assets/62351083/b3f2da8c-5d8f-4c9c-aa52-2f2bc5a025fa)

![image](https://github.com/free5gc/free5gc/assets/62351083/1fb087cd-cc3a-4e76-99ba-3736e72ccc43)


## To Reproduce
Steps to reproduce the behavior:
Deploy Otel Operator, Go Instrumentation, Free5GC (latest) and Jaeger. (all latest versions)
View logs from the otel sidecar container or traces in Jaeger
Observe unusual traces with HTTP PRI method in Jaeger.

## Expected behavior
The HTTP PRI method is definitely unexpected. Other than that, the F5gc works as expected - can see the registered user in the WebUI.

## Environment (please complete the following information):
OS: Ubuntu 20.04 LTS Kernel v 5.15.0-105-generic
Go Version: 1.17.8 (Free5gc)
Version: otel operator latest, same with instrumentation


### PCAP File
Not available yet. I can reproduce this issue if the PCAP is needed.

--- end body ---

None