change ellipsis to 3 dots for ZYTE_API_LOG_REQUESTS text truncation

[BurnzZ]

Motivation: I got confused when looking at the Scrapy Cloud logs since it says I got a request on http://books.toscrape.com/catalogue/category/books/romance_8/in\u2026

Log example:

[scrapy_zyte_api.handler] Sending Zyte API extract request: {"httpResponseBody": true, "httpResponseHeaders": true,
 "customHttpRequestHeaders": [{"name": "Referer", "value": "http://books.toscrape.com/"}, {"name": "Accept", "value": 
"text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8"}, {"name": "Accept-Language", "value": "en"}, {"name": 
"Accept-Encoding", "value": "gzip, deflate, br"}], "jobId": "633164/22/65", "url": 
"http://books.toscrape.com/catalogue/category/books/romance_8/in\u2026"}

It turns out this \u2026 character was the … ellipsis character. What do you think about changing this to 3 dots instead?

[codecov]

Codecov Report

Merging #136 (1c06afa) into main (207fed4) will not change coverage.
Report is 2 commits behind head on main.
The diff coverage is 100.00%.

❗ Current head 1c06afa differs from pull request most recent head b4ce6e0. Consider uploading reports for the commit b4ce6e0 to get more accurate results

@@           Coverage Diff           @@
##             main     #136   +/-   ##
=======================================
  Coverage   98.81%   98.81%           
=======================================
  Files           9        9           
  Lines         673      673           
=======================================
  Hits          665      665           
  Misses          8        8           

Files	Coverage Δ
scrapy_zyte_api/handler.py	97.94% <100.00%> (ø)

[Gallaecio]

Yeap. I love me some Unicode, and I’m pretty sure I did this, but it’s either we get … rendered instead of \u… or we switch to ....