Add Paycall Technologies 055-16 M2M range to Israel metadata

[paycall-apps]

Follow-up to PR #4063 / issuetracker.google.com/issues/544217149.

Release 9.0.37 (commit c9d5f73) adopted the BITIT -> Paycall Technologies rename for 055-20 / 055-21 / 055-802 / 055-862 and added the 0105 international prefix, but the 055-16XXXXX range was omitted.

What this PR adds

resources/carrier/en/972.txt — one new record, in numeric order:

 972552|019mobile
+9725516|Paycall Technologies
 9725520|Paycall Technologies
 9725521|Paycall Technologies

resources/PhoneNumberMetadata.xml — append one branch to Israel <mobile> <nationalNumberPattern> so isValidNumber("+972551612345") returns true:

             9[1-9]
           )
-        )\d{5}
+        )\d{5}|
+        5516\d{5}
       </nationalNumberPattern>
     </mobile>

Why both files

The current pattern on master does not match 5516\d{5} — I decomposed each alternation in the issuetracker comment linked above. Without the <mobile> branch, numbers that this PR adds to the carrier file still fail validation.

Scope

• Three line additions total (+3 / -1), all within the Israel territory.
• No other locales touched.
• No change to fixed-line, no change to formats, no change to short-codes.
• The 055-16 range is M2M under the same MoC authorization letter as 055-20 / 055-21 — see the ticket for the scanned allocation reference.

Note on classification

055-16XXXXX is formally an M2M allocation. We placed it in <mobile> because (a) it is a 55X cellular prefix, (b) libphonenumber has no M2M section, and (c) real end-user handsets dial these numbers and expect isValidNumber to return true. If the maintainers prefer a different type (<voip>, <noInternationalDialling>, etc.), please feel free to re-slot — the practical ask is only that isValidNumber("+972551612345") == true and that 9725516 maps to Paycall Technologies in the carrier file.

Note on metadata/metadata.zip

The same gap exists in the CSV-based metadata inside metadata/metadata.zip. metadata/972/ranges.csv currently has rows for 552[01], 558[06]2, etc. attributed to the paycall operator (from the 9.0.37 update), but no row at all for 5516 — the 551X prefix is unassigned there. operators.csv already lists paycall ; "0105" ; "Paycall Technologies", so when this PR is adopted into the internal metadata source, the corresponding CSV row (something like 5516 ; 9 ; MOBILE ; STANDARD_RATE ; ; false ; "paycall" ; "mobile_2/3/4" ; "IL" ; ; ; GOVERNMENT) should flow through to the next Metadata updates for release commit. We are not touching the zip in this PR per the metadata/README.md note that PRs on that directory are not accepted.

Validation

• ET.parse("resources/PhoneNumberMetadata.xml") succeeds.
• The appended regex 5516\d{5} is 9 digits (matches Israel's <possibleLengths national="9"/>), consistent with the surrounding alternation.

CLA already signed under PR #4063.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.