Generate activities and allow to pass the tag. Use search and activate
everywhere which will allow to walk through objects without killing the cluster
even in case of really big documents.

Alarm can generate a lot of activities, so run them less often then critical
ones.

Also minimise activity hurricane by calling expand directly.

Open Orders are searched using indexation timestamp, which allows to see them
in "windows", and does not repeat expand if not needed.

Another way to generate and update simulation shall be found, especially on
busy sites.

Return a safe html selenium test code (which always fails) to indicate a problem when download a test. This will prevent Zelenium get Stalled during the launch.

Follow up commit e0855913

Code cleaned up from not needed variables.

Key in _local_properties does not have to match key in property sheets. So
just blindly try to migrate everything from _local_properties and *only* from
there.

if self.remote_code_url_list is defined, use Zuite_runSeleniumTest
to build an TestSuite using code downloaded from URLs.

This API permits host your selenium html test code elsewhere (ie.: an ERP5 Instance)

This change permit via URL (or request) define custom base_url, user and password information when generate a test code. This generation can be always be blocked by redefining such information inside the test body itself.

obj._propertyMap() will put property twice in list if it is local property and
it is defined in property sheets.

Also extend test to cover code entries related to local property migration.

Also extend test case to cover exactly what is expected to happen.