This reverts commit a87db49b.

Change max age to 1 hour and 1 day

erp5_search_rank_catalog: do not destroy the previously calculated rank

erp5_search_rank_catalog: Show module content before tools content

erp5_search_rank_catalog: keep default value low, to prevent having huge rank score

In order to apply nexedi/erp5@4115e465
it is needed to upgrade an existing side which only contains func_code

Otherwise, method draw enter an infinite loop if users selected some elements

https://github.com/methodofaction/Method-Draw/tree/463e526dbc6ec48561822fde5dec02e085e86497

This is for *StandaloneDeploymentScriptTest* test suites, which
download a large disk image during slapos node instance step.

For example, on a Wendelin.StandaloneDeploymentScriptTest-Debian.Stretch
test run [1], we can see that the slapos node instance started at
2022-05-13 07:50:30,788 and stopped trying at 2022-05-13 07:51:35,885.

In the last run, slapos node instance failed, especially this promise:

    2022-05-13 07:51:35,701 INFO     slapgrid_cp: 2022-05-13 07:51:35 slapos[3548917] ERROR ERROR '/srv/slapgrid/slappart22/t/cjl/i/1/srv/monitor/private/virtual-hard-drive-url/virtual-hard-drive-url-processed-config.state' not empty, content available at https://[???]:8026/private/virtual-hard-drive-url/virtual-hard-drive-url-processed-config.state
    ...

and if we access this URL, we can see the error:

    [Errno 2] No such file or directory: '/srv/slapgrid/slappart22/t/cjl/i/1/var/virtual-hard-drive-url/update-image-processed.md5sum'

which means that the image is still not downloaded.

testnode still ignore slapos node instance state return code and run
tests anyway, so the test ran and failed later.

This image is 1.8Go, when I tried to download it locally it took
56.41 seconds, so it must be generally almost OK.

By retrying up to 60 times, we give more time for the slapos node
instance step to download the image.

[1]: https://softinst161166.host.vifib.net/cjl-oSgtg7v20D/suite.log

This reverts commit b404b724.

Redirects does not make any sense with timerserver responses, let's
keep this an error.

To workaround a bug with our old pylint / astroid versions

Revert "py3: sortKey() must be a string as comparison between str and None/int/tuple now raises TypeError."

This reverts commit 192c2000.

This commit introduced a test failure with testCommitOrder
testInvalidationBug.TestInvalidationBug [1]

    Traceback (most recent call last):
      File "Products/ERP5/tests/testInvalidationBug.py", line 93, in testCommitOrder
        self.assertEqual(result_list[1], [0,0])  # activity buffer first
    AssertionError: Lists differ: [1, 0] != [0, 0]

    First differing element 0:
    1
    0

    - [1, 0]
    ?  ^

    + [0, 0]
    ?  ^

That commit was apparently in the good direction, because transaction
API specifies that sortKey must return string

https://github.com/zopefoundation/transaction/blob/6cf10102948a8f4e36092a9b402e3859d6db4ccd/CHANGES.rst#141-2013-02-20
https://github.com/zopefoundation/transaction/blob/33448417ab526327757f05e23b1884786c805629/src/transaction/interfaces.py#L524-L534

using a css selector also matches:

    <div class="transition_message transition_message_success">Deleted.</div>

unlike the xpath selector which matches only element where class
attribute is exactly "transition_message"

Define min and max to integer html field

when defining start and end property in ERP5 integer field

"template_keep_path_list" definition was wrong, the tool is uninstalled
when updating in wrong order

This allows executing a script doing REQUEST.RESPONSE.redirect() without
error.

Before this patch it's an AttributeError similar to:

    ------
    2022-04-12 03:52:49,083 WARNING ActivityTool Could not call method ...
    Traceback (most recent call last):
      ...
      File "Script (Python)", line 34, in Base_redirect
        return request.RESPONSE.redirect(redirect_url, status=status_code)
    AttributeError: TimerResponse instance has no attribute 'redirect'

Instead of temporarily changing the global timeout, which can impact
other parts of the system and which is not free from race conditions (
another thread might have changed the timeout when socket.getdefaulttimeout()
is called and then we restore a wrong default timeout).