fix: add toml double/float/int support

[BoyeGuillaume]

No description provided.

[Tran-Antoine]

Like we discussed there is still an issue at a lower level that prevents us from being able to use anything but Strings, we have to investigate how to fix that

[BoyeGuillaume]

You mean that internally we cannot store anything but strings? Which represents an non-optimized memory usage. I believe we aren't really doing a gigantic database and therefore such issues aren't really relevant

[Tran-Antoine]

No that's not the issue I'm referring to. By lower level, I meant in the code. The problem comes from getDatabaseEntries which prevents us from being able to use anything but strings

[BoyeGuillaume]

This is the same issue. To store information we need to know how to store it. Like if i store a integer if will store 4 bytes. But i can also load this 4 bytes as if it was a string of 4 bytes. We therefore need to introduce a Varient type (type that can contain some objects such as Integer, String, etc...) and from there we will create a way to serialize/deserialize the Varient from the database. The issues with this approach are:

• Require significant work
• We will need to serialize the type as well as the data
• Cannot do that with generic (as we need a way to serialize/deserialize => could work with an interface thought)