RestAPI v3: updated server self-signed ssl certificate.
 - Previous one expired on Aug 6th.
Adapted model in order to better manage harvested data
RestAPI: enabled command reply as API response.
Harvester plugin: extended data extraction to better suit RestAPI response
Batch of small fixes and enhancements:
 - corrected LOG destinations on [Trigger|Command|Reaction]Persistence save methods
 - added capability to remove tuples' elements
 - corrected result colection in Harvester
 - small fixes in RestAPI
 - added shutdown capability through RestAPI
Core-347: add "consumption" behavior to ElectricDevice
 - modified model and core to support the new behavior.
 - adapted Base-Objects and RestAPI plugins
RestAPI v3: revised ReactionResource
Fixed Core-392: Make Statement check fail if trigger filters a property not present in event
Fixed Core-476: Plugin start should execute onStart() user code after framework operations
Fixed Core-477: Fix BehaviorManager and add filterByZone feature
Core-404: plugin uninstaller
 - extended and rearranged client API
 - added Uninstall button in frontend-java PLuginConfigure class
 - added uninstall support as DELETE method in RestApi v3
 - added two translation strings
Partial fix to Core-404 and Core-478. Uninstall regresssion in restapi, not working anymore. Removed the number of plugins in a category in 'Install from marketplace' form
RestApiv3: fixes
 - Made API fully CORS compliant (fixed OPTION method params)
 - Fixed new ReactionResource
Adding various helpers like HttpHelper (retrieve HTML, JSON or XML contents from urls); SerialHelper (improved serial ports communication); TcpHelper (tcp socket with timeout)
Quick fix: removed a not used dependency
Quick fix: right click on a plugin shows its GUI again. This is a temp fix, a better fix is to have multiple menus, one for plugin configuration and one to show its GUI
Fix PL-105: Close button on Login Form
SerialHelper: added feature to receive data in chunks of fixed size or ending with a custom string terminator
Payload check in trigger evaluation now uses a strategy pattern. Added also a BETWEEN_TIME feature that checks if a given time in format HH:mm:ss lays between a time interval in format HH:mm:ss-HH:mm:ss. It works also if the interval crosses day boundaries (midnight is in the middle of the intervall)
Some interface renaming