Reconsider how users use offloadNone strategy while some filters block

[idelpivnitskiy]

Existing approach is that if users specify offloadNone() execution strategy on the builder, we respect that and disable offloading. However, if they have a filter that for sure has blocking code, it will hurt users if we are silent about it. Consider the following improvement options:

• still add offloading based on the filter chain requirements and log that the computed value is different from what was specified;
• throw an exception describing what filter does not allow using offloadNone()
• keep the offloading disabled, but warn users that they have a blocking code in the filter chain

[idelpivnitskiy]

Logging is enhanced in #2224