implement addProject method for MapeoManager class

[achou11]

Closes #209

NOTE: Stacked on #208

Lots of implementation questions:

• my understanding is that adding the project should update the ProjectKeys table in the client db if it's not there. However, how do we get the auth encryption key if that's the case? (which is required in the encryptionKeys column value) EDIT: addressed
• I'm guessing that we don't want to call project.$setProjectSettings() after creating the project instance, like we do in manager.createProject(). If that's the case, does it still make sense to return the project instance in this addProject() method? doing so seems to cause some issues unless I'm missing an important step: EDIT: addressed

TODO:

• Add tests. Not really sure what to test here...Was thinking that there's gotta be some distinction between creating a project and adding a project created by someone else i.e. you don't necessarily have the project secret key + encryption keys for the project (in the latter).
• (non-blocking) wait for fix: invite.encryptionKeys should be required #223 to fix type issue with Invite

[gmaclennan]

Somewhere along the way the API docs got out of date.

addProject() is what we would use when receiving an invite, so the param should be the same type as an invite e.g.

addProject(invite: {
  projectKey: Buffer,
  encryptionKeys: {
    auth: Buffer;
    data?: Buffer | undefined;
    config?: Buffer | undefined;
    blobIndex?: Buffer | undefined;
    blob?: Buffer | undefined;
  },
  projectInfo: { name?: string | undefined }
}

Not sure what to do with projectInfo - once we sync we will get the project info from the replicated cores, but in the meantime it would be good to use the name passed here. Suggestions?

[gmaclennan]

If the project you are trying to add already exists then I think maybe throw? And maybe return the projectId the same as createProject?

[gmaclennan]

Also the proto definitions for Invite need updated - encryptionKeys should be required, since we always need an auth core encryption key. I'll do that now.

[achou11]

Somewhere along the way the API docs got out of date.

addProject() is what we would use when receiving an invite, so the param should be the same type as an invite

Ah this make sense. Figured that something about the method params would need to be updated. I have an issue in the core docs repo (digidem/mapeo-core-docs#14) to track changes that need to be made there as a result of the implementation changes we do here, in case that's helpful (I already added it as an item there to address later)

Not sure what to do with projectInfo - once we sync we will get the project info from the replicated cores, but in the meantime it would be good to use the name passed here. Suggestions?

not sure what suggestions you're looking for, but seems like it would make sense to use whatever's passed there to update the settings of a project via project.$setProjectSettings()

EDIT: discussion with Gregor surfaced the fact that we can't just do the setProjectSettings() call like I thought. Decided on the following:

• Update projectKeys table to have projectInfo column that's a custom json type with name field for now
• Update listProjects implementation to read from the projectKeys table as the source of truth for what projects exist, and cross reference with queried project table to get desired information for return value (no sql join necessary for now)
• Update addProject to save invite.projectInfo to projectKeys table