Perform proper NANP validation in US/CA localflavor phone number

[Dan McGee]

Patch attached.

​http://en.wikipedia.org/wiki/North_American_Numbering_Plan

Long story short:

1-NPA-NXX-XXXX

• NPA: 3 digits, 1st is [2-9], 2nd/3rd are [0-9]. 2 and 3 cannot both be '1'.
• NXX: 3 digits, 1st is [2-9], 2nd/3rd are [0-9]. 2 and 3 cannot both be '1'.
• XXXX: 4 digits, no restrictions.

Former code allowed any digit in all locations, meaning the following bogus phone numbers (now in tests as invalid) were accepted:

'023-234-5678'
'123-234-5678'
'323-134-5678'
'312-034-5678'
'311-134-5678'
'312-211-5678'

[Dan McGee]

Note that this will conflict slightly with #7463, which also makes the US and CA phone number validators stray from each other, which is likely not a good idea.

[Aymeric Augustin]

django.contrib.localflavor is now deprecated — see ​https://docs.djangoproject.com/en/dev/ref/contrib/localflavor/

A repository was created for each localflavor at ​https://github.com/django/django-localflavor-? (Replace with the country code.)

If you're still interested in this ticket, could you create a pull request on that repository?

Sorry for not resolving this issue earlier, and thanks for your input!