Change TASS user activity storage to local database not iotJumpWay

[AdamMiltonBarker]

Currently the process when a user is detected is as follows:

• User is matched against known database of images or marked as intruder
• TASS communicates with iotJumpWay and stores the user ID / name, activity and classification / location etc in the iotJumpWay database.
• TASS devices are able to track the user if there is a camera unit in the room
• Applications can then connect to that database via the API to access data that they are authorised to access

A coming update will swap this activity to using a local database provided and integrated with a future release / push. Scope of this move will include:

• Removal of all identifying information with exception to location on local network and classification (Static Values: Known/Unknown) that is sent to iotJumpWay.
• Changing storage location of user activity data to local MySQL database opposed to iotJumpWay global database.

This move will mean all data that could be used to track trends never leaves your home network but can be utilised by your custom applications.

Related code:

https://github.com/GeniSysAI/Vision/blob/master/Local/LocalStreamer.py

[AdamMiltonBarker]

TASS related issues updated with:

https://github.com/GeniSysAI/Vision/commit/06e6e597aeb2d155389e7d81528a1703ee17dffd https://github.com/GeniSysAI/Vision/commit/ebd436905ec8717164467240317d642a63ed5200

• Removed identifying information being sent to iotJumpWay
• Created local database for user logs and management (See related GeniSys Server repo updates)
• Created MySql helper for database connections
• Improved firewall
• Added tracking information in README

[AdamMiltonBarker]

Server related updates included in:

https://github.com/GeniSysAI/Server/commit/3f3329757dc9d8eb29483523d5b6ce2733e9c2f2