[ENH] More storage options and information

[lakhoune]

1. Motivation -We can only set a name and store a model as that name. The problem with this is that users forget when they have stored the model for the last time and often, I have observed that users will start calling their models: botmodel1 botmodel2 botmodel3, botmodelbackup, botmodelbackup2,... So if you want to use the latest version of a certain model you do not know which one is the latest.
2. Specification - For each model store not only the name but also metadata like the date when it was stored, a version number and the user which stored the model
3. Finalised state - If a user wants to store a model, they click on the store model button. This opens up a form in which the user is able to specify the name and an optional version tag. If they click on submit then this model is stored along with the current timestamp, the username (anonymous if not logged in) the optional version tag. If the user wants to load a model, they can use a search field. The suggestions are based on the search input and also list the version tag if available. A more info button expands the search result to reveal the username and date of submission

[lakhoune]

The API of the bot manager also needs to be updated for the changes

the API store model should expect a json obj with the keys :

• model
• author
• date (iso string)
• tag

The change also needs to be reflected on the database.

[lakhoune]

The API of the bot manager also needs to be updated for the changes

the API load model should return a list of models with the key;

• model
• author
• date (iso)
• tag