fix: stop using f-strings in logs

[danfimov]

Using f-strings to format a logging message requires that Python eagerly format the string, even if the logging statement is never executed. For our case it's especially bad - we use f-string in debug log to print an entire message. For long messages during profiling with py-spy I found 5% or unnesesary CPU usage just for __str__ method on messages (200Kb each).

Other things:

• updated ruff, so now we have more standard rules and fixed couple of issues related to them.
• ignored one more rule rule about argument count

[codecov]

Codecov Report

❌ Patch coverage is 40.00000% with 9 lines in your changes missing coverage. Please review.
✅ Project coverage is 82.55%. Comparing base (9ce2069) to head (1f7e8f7).

Files with missing lines	Patch %	Lines
taskiq/cli/worker/process_manager.py	0.00%	6 Missing ⚠️
taskiq/cli/worker/run.py	0.00%	1 Missing ⚠️
taskiq/middlewares/prometheus_middleware.py	0.00%	1 Missing ⚠️
taskiq/receiver/receiver.py	66.66%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #665   +/-   ##
=======================================
  Coverage   82.55%   82.55%           
=======================================
  Files          69       69           
  Lines        2717     2717           
=======================================
  Hits         2243     2243           
  Misses        474      474           

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

🚀 新建 features to boost your workflow:

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