Mulitple project support

[eddieantonio]

Enable the user to be able to work on multiple different languages/models at the same time.

We used to have UI for a sidebar with different languages that resemebled Slack's workspace picking sidebar (see Figma:

To close this issue, users should be able to create a new project, and switch between their language projects freely.

NOTE: this task might be too large for one issue; sub-issues may be required!

[yehee]

@eddieantonio I might have missed it, but are there any associations currently in place between projects and files storing wordlist sources? I couldn't seem to find any indication as to which project each file belongs to.

[eddieantonio]

@yehee since there only is one "project" right now, there is nothing really explict for multiple projects; however, there is a constant right now that can be used as a "project ID":

predictive-text-studio/src/worker/storage.ts

Lines 10 to 13 in d6486ef

	/**
	* The key of the ONLY StoredPackageInfo record.
	*/
	const PACKAGE_ID = 0;

I believe the files table will need to be changed such that it has a non-null reference to the project it belongs to.

In relational database terms, we'll have two tables:

• files(id, project, name, wordlist)
• projectData(id, langName, bcp47Tag, authorName, modelID, copyright, dictionaryName, version)

And they are related in that there is a many-to-one relationship between files.project and projectData.id. files.project is a foreign key!

There will need to be a data migration that, once files.project is added to the schema, all of the existing files need to have their project set to 0 — the initial project ID.

I don't know if that made any sense >.< please let me know if I can clarify any further!