Runtime DB: refine schema files to be more efficient

[magicDGS]

Currently we have not put too much effort on the entity schemas on the runtime DB, but we can improve the fields to be more in-line with the needs that we have: for example, the setCodes have more or less a fixed size that we can set on the schema to prevent huge memory/disk load that is not required (and we can buffer the limit a bit anyway to prevent crashes if the Konami definitions change).

This is more thinking about the future of the application to have less memory/disk footprint so it is leaner on the github-action that will run the data collection/bundling workflow.

[magicDGS]

Not sure if this will be super important, as the datatypes for SQLite are not really that strict and we are not planning by now to move away to other technology (and in that case we will need to anyway adapt the schemas for whatever we choose).