Expose x-ms-client-request-id

For those of us who may be thinking about building automation around blobporter, it would be very useful if you could expose the _x-ms-client-request-id_ header as an optional input parameter. This would assist with log correlation etc.

No file or test is named. Start by tracing how blobporter accepts optional inputs and constructs Azure Blob Storage requests; then verify that a supplied x-ms-client-request-id reaches the request for log correlation and that the default behavior remains unchanged.

Written by the indexing model from the issue text.