Clarify how Receivers must handle errors returned by Consume*() functions

[tigrannajaryan]

This is important to make sure failed Consume*() calls are correctly handled
by Receivers and that the Receives in turn correctly respond back to the senders
from which they received data.

We may need to audit all receivers to make sure they work according to these
requirements.

[codecov]

Codecov Report

Merging #4267 (d4e1a05) into main (c64e6ae) will decrease coverage by 0.89%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #4267      +/-   ##
==========================================
- Coverage   88.20%   87.31%   -0.90%     
==========================================
  Files         173      176       +3     
  Lines       10327    10618     +291     
==========================================
+ Hits         9109     9271     +162     
- Misses        978     1106     +128     
- Partials      240      241       +1     

Impacted Files	Coverage Δ
service/collector.go	66.26% <0.00%> (ø)
model/pdata/generated_common.go	100.00% <0.00%> (ø)
model/pdata/generated_resource.go	100.00% <0.00%> (ø)
config/configauth/mock_clientauth.go	100.00% <0.00%> (ø)
config/configunmarshaler/defaultunmarshaler.go	100.00% <0.00%> (ø)
service/parserprovider/inmemory.go
service/parserprovider/default.go
service/parserprovider/properties.go
service/parserprovider/file.go
service/parserprovider/expand.go
... and 18 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c64e6ae...d4e1a05. Read the comment docs.

[bogdandrutu]

I think we need a similar section to the Processor, also we should describe the async case like "batch".