[FEATURE] Add textable status to API

[danry25]

What is the problem that this feature solves?
Trying to determine if a phone number is textable.

Describe the solution you'd like
If the carrier is market as Wireless or has a PCS or wireless OCN then the number is textable. If the phone number has a SMS enablement then it is also textable (lookup NNID or use Twilio Lookups API to determine).

How will this improve revenue or reduce our costs?
This will provide a richer dataset for us to sell customers.

[uncheckederror]

The possible line types are defined here: https://www.twilio.com/en-us/blog/filter-voip-before-otp-verification

[uncheckederror]

Per https://www.twilio.com/docs/lookup/v2-api/line-type-intelligence#type-property-values

"Carrier data is not available for phone number types: personal, tollFree, premium, sharedCost, uan, voicemail, pager, or unknown. In these cases MobileCountryCode, MobileNetworkCode, and CarrierName values will be null."

In all of these cases and for landline our API will report that the number is not SMS enabled.

We will report that SMS enablement is true for mobile, fixedVoip, and nonFixedVoip.

@danry25 is this correct?

Not sure how to lookup NNID.

[danry25]

SMS enablement is always true for Mobile, but for fixedVoip and nonFixedVoip we need to do another lookup to determine if there is an over the top SMS enablement.

We can get a crummy version of this data out of Twilio Lookups API, but really we need to be checking the NNID so I should get an API for that lookup type. For now do we want to leave this portion unimplemented?