Draft: [REF] Removing secdb from MySQL to a regular file in the system

Goals to achieve

• Speed up Tiki installation by not loading secdb to MySQL
• Speed up and reduce Tiki MySQL dumps size
• Have a file compatible to md5sum to quick check Tiki files consistency
• Have a file compatible to md5sum to help on quickly testing the released tarballs

Todo

• create console.php command to verify current files from secdb
• create console.php to directly get secdb from gilab (based on tiki version) and check the local files

Things removed

1. severity column - currently it seems to be not used, and it has no value set in current SQL dumps
2. version column - Now we get the version from the file name. According to the function generating the current secdb, the version written in the filename is always equals to the version written into the SQL column, so no reason to this redundancy. Also, after upgrading Tiki, it is impossible to have different versions for the same file in the secdb, as the current sql starts with DELETE FROM tiki_secdb;