Create JSON API v2

Problem/Motivation

The current JSON API for events leaves out a lot of important information about players, especially LMS ID and ECF rating code.

It also follows an eccentric format (e.g. games represented by tabular arrays rather than objects with named fields) and does not follow REST conventions (e.g. it requires POST with a JSON object in the body to supply parameters).

Proposed resolution

I would like to design and implement a new JSON API which allows access to entities like organisations, seasons and events with a wider range of information, and a more extensible format.

I think it makes sense to add a mechanism for API keys to be created and associated with an owning LMS user. Requiring the use of API keys on all requests allows all API usage to be associated with a real-world identity, and makes it possible to selectively disable malicious usage without impacting other users. To begin with, an API key can give the same access level as its owning user, but if necessary, in the future a more sophisticated permission model could be built.