error.type - clarify how an exception type is represented

[JamesNK]

error.type doesn't say how an exception should be represented.

I see that the logs spec says that exception.type should have the fully qualified class name (i.e. class name + namespace):

semantic-conventions/docs/exceptions/exceptions-logs.md

Line 43 in b127e12

| `exception.type` | string | The type of the exception (its fully-qualified class name, if applicable). The dynamic type of the exception should be preferred over the static type in languages that support it. | `java.net.ConnectException`; `OSError` | See below |

error.type allows exception information to be set, but doesn't specify whether the type should be just the name or be fully qualified.

I think error.type definition should be updated to be more specific, like logging's exception.type.

Before:

semantic-conventions/docs/http/http-spans.md

Lines 132 to 133 in b127e12

	**[1]:** If the request fails with an error before response status code was sent or received,
	`error.type` SHOULD be set to exception type or a component-specific low cardinality error code.

After:

**[1]:** If the request fails with an error before response status code was sent or received,
`error.type` SHOULD be set to exception type (its fully-qualified class name, if applicable) or a component-specific low cardinality error code.

[JamesNK]

cc @lmolkova