Disable deprecation warnings when running in production envs

[acelaya]

Closes #2373

Enable error reporting for any kind of error in dev and test envs, but disable reporting of deprecation warnings in production.

This is needed because the ProblemDetailsMiddleware wraps the whole execution in an error handler which converts any reported error into an ErrorException. See https://github.com/mezzio/mezzio-problem-details/blob/68a17a0/src/ProblemDetailsMiddleware.php#L101-L118

It is good to know about deprecation warnings when in dev, as those need to be eventually fixed, but in production, they should not cause the whole request to fail.

Todo

• Verify this indeed fixes Shlink 4.4.4 failing to acquire lock with Redis cluster when TLS connection to the Redis cluster is enabled #2373, and allows short URLs with tags to be created when using redis with an encrypted connection.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.87%. Comparing base (449a588) to head (a18360a).
Report is 3 commits behind head on develop.

Additional details and impacted files

@@            Coverage Diff             @@
##             develop    #2375   +/-   ##
==========================================
  Coverage      93.87%   93.87%           
  Complexity      1707     1707           
==========================================
  Files            277      277           
  Lines           5915     5915           
==========================================
  Hits            5553     5553           
  Misses           362      362           

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