Bug 925404 - [B2G] [SMS] Always include the phone number in the SMS Thread UI, even if the carrier is known. r=schung

* Using new phone format everywhere;
* Using different color for carrier name in the thread view header;
* Removed a bunch of unsed code.
If it's able to apply ```data.number``` here, how about changing SharedComponents.phoneDetails interface to accept object as first parameter with number/type/carrier properties? Then you can set data/recipient/detail directly to phoneDetails to create phoneDetailsHTML. But the drawback is we can't guarantee the properties is matched  between different api. wdyt?