RemoteEvent.get Caching

[bjendres]

For event list queries (e.g. "all events that still have open sports") we should allow for short-term caching, provided the request doesn't contain a personalised token.

Currently there is no such caching in the API, the runtime might be high, and the results don't vary too much. Therefore a cache based on the complete request, with a short TTL (e.g. 10 seconds) could improve performance on highly frequented systems.

Of course, any changes to events and/or participants should invalidate the cache.

The fact that people spend 10's of seconds on the registration form alone, illustrates that an additional cache with short TTL shouldn't have too much impact on the overall user experience.

[jensschuppe]

Moving to 1.3 as 1.2 is already in beta.