Suggestion: Separate arfs and ardrive-core-js -libs

[Silanael]

It would be nice to have a properly established API to allow easy interaction with ArDrive for external developers.

Upon moving towards this goal, I would suggest to separate the current ardrive-core-js into two libraries:
One that would contain the absolute essentials to interact with ArFS without database management, while the other one would be a base library for the ArDrive's official application suite, essentially what current ardrive-core-js is.

This suggestion stems from my own experience of using ardrive-core-js - an utility I wrote had no need for database or even a concept of a user, yet I found that most of the functions in the lib required these to be present (I got around this by creating a dummy user, kinda dirty hack).

The arfs-lib would contain functions to create, upload, download and interpret ArFS-compatible transactions and the metadata .json that would operate on TXIDs, File-IDs etc. alone, leaving the user/database management-aspect to the developer to implement in their own way.

ardrive-core-js would be a more comprehensive suite for building applications with ArDrive-support, focusing on ease of use and a standardized way of doing things.

Just something to consider.