This will prevent the input gadget to be changed if its parent call render with the same value (as ERP5 does in case of formulator error).

Display the update button if an action is defined.
Send the 'update_method' in the query in this case.

/reviewed-on nexedi/erp5!559

-  remove hack when tests were using each others data by `markChanged` script

in erp5_run_my_doc, erp5_web_blog and erp5_credential

Same reason as in 2115abc3.

/reviewed-on nexedi/erp5!554

This avoids relying on implementation details by only relying on regular
API. This test should now be more robust in face of implementation changes.

Also, add an XXX about manage_test annoying behaviour.

Avoids the double-nonsense of looking the document up by path inside callee (!)
using the catalog (!!).
Also, follow naming conventions: variables containing documents should end
in _value, not in _object.

Vincent Pelletier:
- commit message
- remove unrelated change
- squash similar similar-intent commits even though they apply to
  different BTs

These methods must not be called synchronously:
- they can break catalog by not being careful enough about other
  reindexations which may happen in parallel. See the serialization_tag
  mechanism for more.
- indexation gets executed in the security context of the user causing the
  call, which may lead to an indexation result different from what happens
  when indexation happens with an all-accesses user.
These lines of code (some even commented-out) give a bad example. Replace
them with safe equivalents.