client: set authorization header from the URL

[niklasad1]

Close #1371

The rationale is to unify the behavior how cuRL, browsers and similar are handling username and passwords from URLs.

Testing

curl

$ curl -sSG "http://user:pwd@localhost:9944"
2024-05-31 09:25:59.366 TRACE tokio-runtime-worker jsonrpsee-server: Request { method: GET, uri: /, version: HTTP/1.1, headers: {"host": "localhost:9944", "authorization": "Basic dXNlcjpwd2Q=", "user-agent": "curl/8.2.1", "accept": "*/*"}, body: Body(UnsyncBoxBody) }

jsonrpsee ws client

$ jsonrpsee-ws
2024-05-31 09:28:32.016 TRACE tokio-runtime-worker jsonrpsee-server: Request { method: GET, uri: /, version: HTTP/1.1, headers: {"host": "localhost:9944", "upgrade": "websocket", "connection": "Upgrade", "sec-websocket-key": "amixRuJIg8sPqd0K2tNSTw==", "authorization": "Basic dXNlcjpwd2Q=", "sec-websocket-version": "13"}, body: Body(UnsyncBoxBody) }

jsonrpsee http client

$ jsonrpsee-http 
2024-05-31 09:39:21.580 TRACE tokio-runtime-worker jsonrpsee-server: Request { method: POST, uri: /, version: HTTP/1.1, headers: {"content-type": "application/json", "accept": "application/json", "authorization": "Basic dXNlcjpwd2Q=", "host": "localhost:9944", "content-length": "62"}, body: Body(UnsyncBoxBody) }