Cosmos response headers uses the wrong header key

[justinbarclay]

I ran into an error when running your cosmos db examples.

For example, when running

cargo run --example document_entries_00 test test

I'd get the output:

Created 5 documents.
Error: AzureCoreError(HeaderNotFound("x-ms-max-item-count"))

Which means it was failing when listing documents.

After doing a lot of digging around, more than I'd like to admit, I came to the conclusion that your CosmosDB response headers are set up incorrectly.

For example, here, you call a function item_count_from_headers. This function checks for the HTTP header "x-ms-max-item-count", which is an optional request header. Instead, I think "x-ms-item-count" is meant to be the response header.