Add a lazy cache for Intl objects on MessageContext

[zbraniecki]

Now that we have a proper PluralRules object, we should cache it on MessageContext.

[zbraniecki]

Ehh, this ends up being a very non trivial task.

I spent way too much time today on #rust trying to understand the limitations. It boils down to - it's not easy/possible to have a single cache for different types. If all our formatters had the same set of methods, we could do this with impl Trait and trait object.
But in the world where we have PluralRules.select and DateTimeFormat.format, it's very hard.

It is possible to use an enum here, in a closed model which will not allow third-party devs to add their own formatters (or at least, they wont be cached).

Unfortunately, that requires us to change the mutability of ctx and env in resolver, because now any call can trigger adding an object to cache, so you have to pass mut env all around.

@stasm - would you be interested in taking a look at this? Maybe you'll come up with some better model for this problem, because I feel like I'm out of ideas :(

[stasm]

We'll need some kind of mutability for env (via mut or RefCell maybe?) for #21, too. I'll first look into #21 and perhaps it will give us some ideas for this issue.

[mmstick]

What needs to be cached, exactly?

[zbraniecki]

nothing yet for we don't have any intl formatters. It's likely going to be delayed till later.

We're about to switch fluent to use https://github.com/unclenachoduh/pluralrules which will be the first intl formatter and it will not require any caching for now.

[zbraniecki]

but once we get intl date time formatting and number formatting we'll likely want to cache the instantiated structures.

[zbraniecki]

@mmstick with @unclenachoduh landing of the intl-pluralrules crate use, now we have a good candidate.

Every comparison that involves a PLURAL builtin renegotiates locales and regenerates IntlPluralRules instance: https://github.com/projectfluent/fluent-rs/blob/master/fluent/src/types.rs#L60-L67

Instead, we should do what we do in JS: https://github.com/projectfluent/fluent.js/blob/master/fluent/src/context.js#L212-L222

There are subtle differences - JS uses an Options bag, we just pass one argument, JS does language negotiation inside the constructor, we do it externally, but it boils down to the same.

We want to do it once, and for the given PluralRulesType cache the instance on the MessageContext.

The trick is that in the perfect world, we'd like to make the mechanism flexible enough to handle some sort of Intl.DateTimeFormat and Intl.NumberFormat equivalents in the future once Rust gets them.
But I guess we can also start with a cache just for PluralRules for now.

Wanna take a stab at it?

[zbraniecki]

I was able to fix it trivially for now in 7b0cd65