🛠 Tooling: Consider splitting into a monorepo and separating "data" vs. "generation" packages

[JoshuaKGoldberg]

Bug Report Checklist

• I have tried restarting my IDE and the issue persists.
• I have pulled the latest main branch of the repository.
• I have searched for related issues and found none that matched my issue.

Overview

Right now, if you add a dependency on the emoji-platform-data package, you also get transitive dependencies on emojipedia -> graphql-request -> quite a few GraphQL-related packages. Which is not great. Users who just want the static emoji exports probably don't want all the dependencies for the emojipedia package's Node.js API.

I think it'd be good to rethink how these two packages are organized. Once I finish setting up https://github.com/JoshuaKGoldberg/emoji-blast as a monorepo, I'd like to tackle re-organizing this one. I think there should be a split between code that generates emoji data vs. packages that export the generated data.

Maybe the split could be something like...

• @emoji-platform-data/* (e.g. @emoji-platform/data/emojipedia): just the data exports
• emoji-platform-data: exports all generation APIs

...I'll need to think more on this.

Additional Info

💖