Add support for ProgressTracker

[amosjpa]

Greetings taskiq-nats team,

This PR adds support for ProgressTracker in nats - it's a simple change that follows the existing usage patterns for storing results in the object store. It uses a prefix of progress:<task-id> to avoid conflicts with the result entries (which are just keyed by <task-id>).

The motivation is that we are using taskiq and testing various backends, and we'd like to have datapoints for nats.

[XChikuX]

I don't understand your full usecase.

What do you mean by:

we'd like to have datapoints for nats

And what progress are you tracking?

[danfimov]

Thanks for the contribution. Sorry for a long review)

[danfimov]

@XChikuX About progress tracking: https://taskiq-python.github.io/guide/state-and-deps.html#exception-handling

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.46%. Comparing base (0bb7640) to head (bcfa45d).
⚠️ Report is 3 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master      #25      +/-   ##
==========================================
+ Coverage   97.34%   97.46%   +0.12%     
==========================================
  Files           4        4              
  Lines         188      197       +9     
==========================================
+ Hits          183      192       +9     
  Misses          5        5              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.