HTTP semantic convention stability migration for fastapi

[lzchen]

Part of #2453

[emdneto]

For reviewers: I did some runs of fastapi instrumentation using this branch and the current version available

Current version (0.46b0) - No opt-in

"attributes": {
        "http.scheme": "http",
        "http.host": "127.0.0.1:8000",
        "net.host.port": 8000,
        "http.flavor": "1.1",
        "http.target": "/foobar",
        "http.url": "http://127.0.0.1:8000/foobar",
        "http.method": "GET",
        "http.server_name": "localhost:8000",
        "http.user_agent": "curl/7.68.0",
        "net.peer.ip": "127.0.0.1",
        "net.peer.port": 40220,
        "http.route": "/foobar",
        "http.status_code": 200
    },

New version 0.47b0.dev (with the changes from this PR)

Default

"attributes": {
        "http.scheme": "http",
        "http.host": "127.0.0.1:8000",
        "net.host.port": 8000,
        "http.flavor": "1.1",
        "http.target": "/foobar",
        "http.url": "http://127.0.0.1:8000/foobar",
        "http.method": "GET",
        "http.server_name": "localhost:8000",
        "http.user_agent": "curl/7.68.0",
        "net.peer.ip": "127.0.0.1",
        "net.peer.port": 33188,
        "http.route": "/foobar",
        "http.status_code": 200
    },

New semconv

"attributes": {
        "url.scheme": "http",
        "server.address": "127.0.0.1:8000",
        "server.port": 8000,
        "network.protocol.version": "1.1",
        "url.path": "/foobar",
        "url.full": "http://127.0.0.1:8000/foobar",
        "http.request.method": "GET",
        "user_agent.original": "curl/7.68.0",
        "client.address": "127.0.0.1",
        "client.port": 45854,
        "http.route": "/foobar",
        "http.response.status_code": 200
    },

HTTP Dup

"attributes": {
        "http.scheme": "http",
        "url.scheme": "http",
        "http.host": "127.0.0.1:8000",
        "server.address": "127.0.0.1:8000",
        "net.host.port": 8000,
        "server.port": 8000,
        "http.flavor": "1.1",
        "network.protocol.version": "1.1",
        "http.target": "/foobar",
        "url.path": "/foobar",
        "http.url": "http://127.0.0.1:8000/foobar",
        "url.full": "http://127.0.0.1:8000/foobar",
        "http.method": "GET",
        "http.request.method": "GET",
        "http.server_name": "localhost:8000",
        "http.user_agent": "curl/7.68.0",
        "user_agent.original": "curl/7.68.0",
        "net.peer.ip": "127.0.0.1",
        "client.address": "127.0.0.1",
        "net.peer.port": 49964,
        "client.port": 49964,
        "http.route": "/foobar",
        "http.status_code": 200,
        "http.response.status_code": 200
    },

[emdneto]

I have identified two issues that are out of the scope of this PR:

1. We are setting url.full for server spans in opentelemetry-instrumentation-asgi. In the new semconv, this attribute isn't necessary for server spans.
2. We are not handling exceptions in opentelemetry-instrumentation-asgi, so if exceptions occur, we won't have the error.type attribute emitted.

Will create the issues for this