This reverts commit c49cf8d8.
Callee is directly accessed from other places, so changing this API is
wrong.
This it not immediately visible in tests, but this makes
erp5_officejs_support_request_ui_test:testFunctionalSupportRequest
testCheckComment test randomly fail (apparently because the javascript
error message may appear after or before the test final step is
satisfied - which means this tests is bugged, but that's a separate
issue).

These variables are only used when they evaluate as true, so it is
pointless work to replace them with empty lists.

Catalog used in this test is now close/above 1k rows, so go one API level
down to get control over that pesky "limit 1000".

These tests do not test what they advertise anymore. Advertised features
are in widespread use in other tests, so there should be no need to test
specifically for these.
Also, avoids polluting other tests by clearing catalog for futile reasons.

ZSQLCatalog/ERP5Catalog is only supposed to work on catalog table, by
definition.

Also, reorder imports to follow python style: standard modules before
others.

Current scheme causes paths to exceed catalog limit.

Especially, stop using getToolByName.

Id generator is too expensive to use for such trivial purposes.
Also, this was using an API of id generator which should never have been
added.
Also, this was bogus on several accounts:
- if the tag as provided by caller (as seems to be supported), then
  newActiveProcess would have used an unrelated tag.
- if the alarm activity fails and gets re-run later, the wrong tag will
  also be used.
Instead, generate the tag with a random value.

This allow to customize browser look.

Make the label, listbox, panel more readable.

2.0.3 could not be installed because 'version.txt' was missing.

* form_list: Jump, Actions, Add, Export, Fast Input
* form_view: View, Actions, Export, Previous, Next
* form_view_editable: View, Actions, Add, Previous, Next

This allow to keep the previous/next links in all mode.

Move the delete functionnality to the action page.

Tic'ing mid-hot-reindex is not possible, so immediate reindexation is
not avoidable here. Also, immediate indexation of just-created document
is acceptable, so this is not exactly a bad example.

Fixed commit was part of a larger commit stack, and this fix was
mistakenly squashed in an unrelated commit, and hence did not make it to
master.