Storing Directus metadata in a different database and keeping user database clean

Summary Directus is already quite a great product. I must say that the way things are being done is really great compared to some alternatives solutions. But as we all know there is always room for enhancements and improvements. I was reading through nocodb's architecture and saw this. The arechitecture looks pretty much like the one of Directus except that they keep metadata in a different database. If user doesn't specify anything for that metadata database at the start of the project, they just store everything metadata related in a sqlite database. And afterwards the user can connect to his database. And that one is just introspected, nothing is done in it, no table created. I think it would be really great to adopt that kind of structure in Directus. So that directus_ tables will be stored in another database (the directus metadata database, preferably sqlite). And the user-defined tables would stay clear in another database. It could make things somewhat more fu…