Refactor Number into separate languages

[doenietzomoeilijk]

The old Number\Ordinal is no longer directly responsible for the ordinal string
generation. Instead, it'll use a dynamically included closure for that. Closures
for English and Dutch are included.

Intended as Proof of Concept, but I can see this working.

Relates to #39

[norberttech]

@doenietzomoeilijk that looks good, I would just suggest to replace callbacks with Strategy Pattern
Each strategy can be registered in builder or even better resolver under specific locale and used according to passed value.

[doenietzomoeilijk]

@norzechowicz I did start out thinking about doing the localized parts in objects, but decided against it, as it involved a whole lot more code and i couldn't think of a way to have it all work automatically.

I might come up with an idea, later this weekend.

[norberttech]

👍

[doenietzomoeilijk]

@norzechowicz How about this? I'll still need to refactor the actual call back to something involving __toString() to keep BC, but other than that this should be less hacky than the closures.

(Real life happened for a week, sorry for the silence on my end).

[norberttech]

@doenietzomoeilijk thanks and orry for late response 🍻