fixes bug #1519

[davidsenk]

Fixes the authorization error with b2 application keys.

Tested with s3proxy and curl

https://issues.apache.org/jira/projects/JCLOUDS/issues/JCLOUDS-1519

gaul/s3proxy#298

[gaul]

@davidsenk Please investigate CI failures.

[gaul]

Looks like some kind of over-strict ordering:

expected:<{"[accountId":"ACCOUNT_ID","bucketName":"any_name_you_pick","bucketType":"allPrivate]"}>
but was:<{"[bucketName":"any_name_you_pick","bucketType":"allPrivate","accountId":"YOUR_ACCOUNT_ID]"}>

[davidsenk]

@gaul resolved, https://github.com/davidsenk/jclouds/actions/runs/7953299249

there were a few bad assumptions in the test requests. YOUR_ACCOUNT_ID is returned in authorize_account_response.json, which is then not used in a few of the *_request.json payloads.

Additionally, the mockwebserver does not get the content-type headers set throughout the test. The "easiest" solution is to fix it so that the mock assert is only looking for application/unknown (default in mockhttpserver).

https://square.github.io/okhttp/3.x/mockwebserver/okhttp3/mockwebserver/MockResponse.html

https://github.com/square/okhttp/tree/master/mockwebserver

[gaul]

Thank you for your contribution @davidsenk!