[erp5_web_monitoring] Fix concurence problem on destroy OPML while sync is running or start just after

If Sync start in background and destroy OPML is launched, some data can be removed while sync is writing. So we prevent sync to run if destroy OPML is running and also, we refuse to destroy OPML if sync is running.

If the search result is only one item, redirect to the item view page, else redirect to the list of that items and let user choose the good one.

Monitor Jio storage has been updated to fix monitoring global Json files and set correct portal_type to it. The fix allow to keep backward compatibility with old/non updated monitoring backend instance.

Clean up the macros and add description to make them more readable.
Precise where the filter/sort editors are located.
Add macros to manage the filter panel.

Its bad to access file from filesystem.

Just a typo probably

erp5_mrp: Fix naming to Simulation Movement test Production Simulation Rule

erp5_mrp: Have ProductionSimulationRule works without items

erp5_mrp: Transformation Simulation rules is adapted to use Manufacturing Order

erp5_mrp: Manufacturing Execution can have Production Order as causality

erp5_mrp: Causality is displayed on Manufacturing Order

make all javascript code compliant with jslint
use renderjs declarejob instead of rsvp defer
use RSVP.delay in replacement of setTimeout for background sync
factorise opml add/view gadget and remove global OPMLManage

Use allDocs to navigate through hosting subscription and import OPML configurations.