Mechanism logic update for managing files

[renhiyama]

Considering most files transpiled and stuff are essentially very small files, and large in numbers, it's not uncommon for esm.sh server to hit its inode limit. I've researched online, and found out that a better way to manage this type of scenario is to use a database system to save multiple file data all together at once and lower the overhead problem and inodes limitations too. I'm currently on a vacation, and just saw the notification about inodes issue back in town, so if @ije can't make an fs driver or something to fix this, I'll look into it myself when I get back.

Setting up a database could introduce more ram usage I think, but will fix the inodes issue for real this time.