add new AnyResponse

[BurnzZ]

A way to address zytedata/zyte-spider-templates#25.

Related PRs:

• create a weak_cache in Injector scrapy-poet#184
• support AnyResponse scrapy-plugins/scrapy-zyte-api#161
• support AnyResponse zytedata/zyte-spider-templates#28

Not quite sure if we should have a detailed documentation about this class in the tutorials since it may be deprecated in the next few months when Zyte API handles Auto-Configuration (i.e. selecting the best extraction source between HttpResponse and BrowserResponse). EDIT: Added docs.

[codecov]

Codecov Report

Merging #195 (27b594e) into master (d783365) will increase coverage by 0.02%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #195      +/-   ##
==========================================
+ Coverage   98.44%   98.46%   +0.02%     
==========================================
  Files          30       31       +1     
  Lines        1414     1437      +23     
==========================================
+ Hits         1392     1415      +23     
  Misses         22       22              

Files	Coverage Δ
web_poet/__init__.py	100.00% <ø> (ø)
web_poet/page_inputs/__init__.py	100.00% <100.00%> (ø)
web_poet/page_inputs/response.py	100.00% <100.00%> (ø)

[kmike]

Not quite sure if we should have a detailed documentation about this class in the tutorials since it may be deprecated in the next few months when Zyte API handles Auto-Configuration (i.e. selecting the best extraction source between HttpResponse and BrowserResponse).

I think we need to have docs for this class; I'm not sure it makes sense to deprecate it later. It shouldn't be only about the extraction source, it should be possible to use this dependency without any extraction as well. The logic is the following: if there is BrowserResponse dependency in the plan, BrowserResponse is going to be used; if not, it probably should use HttpResponse.

[kmike]

Looks good, thanks @BurnzZ!