Repair setcontent

[xiaohutai]

Fixes issues #282 and #283

This PR removes some type hints which is not a nice thing to do in general, but I don't know how to circumvent these issues in a nice way. Below is a summary.

Notes

• At the moment, setcontent can return null or Content for single item when using {contenttype}/{id} or QueryResultSet (empty or not) for multiple items.

  This was changed in 82244ab#diff-5ee7c092d66585260210d467fb97c416

• Function parseValue can get an integer when using where { id: 1 }.

  This was changed in ce98e9b#diff-9501bf2bce92196e20149014404e59fb

• Function getContentForTwig actually gets three parameters:

  1. the base part like pages or pages/1
  2. parameters like printquery, paging
  3. actual where parameters taken from ... where { foo: bar } ...

  This was changed in 1624cdc#diff-47ee526d7c161782611f5afd2e66c76d

[JarJak]

the base part like pages or pages/1
parameters like printquery, paging
actual where parameters taken from ... where { foo: bar } ...

Could you explain those e.g. in the comment above getContentForTwig?

[xiaohutai]

No need for typehinting in phpdoc if they already exists, right?

[JarJak]

@xiaohutai if checkers won't complain, yes

EDIT: actually they complain so please add them

[xiaohutai]

It's stricter than I thought 😅

[bobdenotter]

Works like a charm! 👍

[bobdenotter]

(And my apologies for breaking stuff ;-) )

[xiaohutai]

No, worries. It's actually to show that it's PHPStan complaining about things. Unless those parts are coded differently we can't really add those nice type hints yet.