JMAP Core server implementation

## Things to consider

Below are things I believe would make library more useful.

- go-jmap should avoid enforcing certain storage design and definitely must not provide storage implementation itself. I think it is best to simply translate API requests into corresponding method calls on some interface called "Backend" (see [go-imap](https://github.com/emersion/go-imap) for a good example of how this could be done).

- go-jmap should avoid enforcing certain authentication design and definitely must not provide authentication implementation itself. As with previous point, authentication should be implemented by calling out into user-provided interface implementation.

- go-jmap should rely only on net/http for HTTP server. Use of more advanced frameworks will make it easier to violate the first point.

- JMAP Core, JMAP Mail, etc implementations should be kept independent of each other for extensibility purposes. JMAP is not only about email.

首先检查仓库结构，并将其预期的服务器设计与 issue 中链接的 go-imap 示例进行比较。定义用户提供的存储和身份验证所需的入口点与接口，然后检查 HTTP 处理是否使用 net/http，以及 JMAP Core 是否仍独立于其他 JMAP 实现。

由索引模型根据 Issue 内容生成。