Download Dataset with POST Access and signedUrl not incrementing download count

[ekraffmiller]

Downloading a zip of a dataset from the Modern UI isn't triggering an increment of the download count.
It can be reproduced by making the same API calls as the UI, below.

What steps does it take to reproduce the issue?

1. create a dataset with a file and publish it

2. Check that the download count:
   curl -sS
   -H "X-Dataverse-key: $API_TOKEN"
   "$SERVER/api/v1/datasets/$DATASET_ID/download/count" | jq .

3. Do a post to get the signed URL
   SIGNED_URL="$(
   curl -sS -X POST
   -H "X-Dataverse-key: $API_TOKEN"
   "$SERVER/api/v1/access/dataset/$DATASET_ID?format=original"
   | tee /tmp/dataverse-signed-url.json
   | jq -r '.data.signedUrl'
   )"

echo "$SIGNED_URL"

4. Use the signed url to download the file:
   curl -fL
   -o /tmp/dataset.zip
   "$SIGNED_URL"

5. Check the download count again, it isn't incremented:
   curl -sS
   -H "X-Dataverse-key: $API_TOKEN"
   "$SERVER/api/v1/datasets/$DATASET_ID/download/count" | jq .

• When does this issue occur?
  From the Modern UI, downloading zip file from a dataset

• Which page(s) does it occurs on?
  Dataset page

• What happens?
  download count is not incremented

• To whom does it occur (all users, curators, superusers)?
  all

• What did you expect to happen?
  should increment count

Which version of Dataverse are you using?

Any related open or closed issues to this bug report?

Screenshots:

No matter the issue, screenshots are always welcome.

To add a screenshot, please use one of the following formats and/or methods described here:

• https://help.github.com/en/articles/file-attachments-on-issues-and-pull-requests

Are you thinking about creating a pull request for this issue?
Help is always welcome, is this bug something you or your organization plan to fix?

[qqmyers]

Can we finish the review/QA of #12479 before digging into this? It's possible that it will solve it, but, if not, it will be a merge mess if we fix it in the current code.