Ported Text Segmentation and Unicode Regex Parser

Note:
- Separating CodePoint data is still WIP. I'm sending in a PR before completing it so that the review process can start while I figure it out.
- All the tests are based on their counterparts in twitter-cldr-rb.
- Since Range is not a data type in JavaScript (yet), I made a light implementation of Range in TwitterCldr.Range. Is this the best way?

Special Note:
- Before this gets merged into the master, the data separation for CodePoint needs to be completed as injecting the CodePoint resources here makes the total bundle size ~3.4MB, which is too much. @KL-7 and I discussed this over email and agreed that Text Segmentation should be an opt-in feature that requires a spearate file (with all the CodePoint resources ~2.5MB).
I'm on the fence with this one. Neither solution seems perfect, honestly.
This one is more concise with lesser scope for error because there are lesser constants involved. 
Using alphabet explicitly is more readable.

Your suggestion wins, I feel. 
I'm changing this to 
``` coffeescript
      d : (char for char in [48..57]) # digits 0-9
      w : (char for char in [97..122].concat([65..90]).concat([48..57]).concat([95])) # lowercase, uppercase, numbers
```