Group Microsoft/OneDrive no-PTR ranges into one district

OneDrive's IPs (e.g. 13.107.x, 150.171.x) have no PTR and weren't in our
CIDR table, so each fragmented into its own IP-named district — a long
session showed dozens, all with the "OneDrive" process subtitle. Add the
documented Microsoft 365 service ranges so they collapse to one Microsoft
district. Deliberately excludes generic Azure tenant space, which would
mislabel third-party apps hosted on Azure.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Sources/NetworkCityCore/IPRanges.swift

@@ -13,6 +13,16 @@ public enum IPRanges {
         ("149.154.160.0/20",  "telegram",   "Telegram"),
         ("91.108.0.0/16",     "telegram",   "Telegram"),
         ("13.64.0.0/11",      "microsoft",  "Microsoft"),
+        // Microsoft 365 / OneDrive front-ends — no PTR, so without these each
+        // IP fragments into its own district. These are Microsoft-operated
+        // service ranges (not generic Azure tenant space, which would wrongly
+        // relabel third-party apps hosted on Azure).
+        ("13.104.0.0/14",     "microsoft",  "Microsoft"),   // incl. 13.107.x
+        ("150.171.0.0/16",    "microsoft",  "Microsoft"),
+        ("52.108.0.0/14",     "microsoft",  "Microsoft"),   // O365 common
+        ("52.112.0.0/14",     "microsoft",  "Microsoft"),   // Teams/Skype
+        ("40.96.0.0/13",      "microsoft",  "Microsoft"),   // Exchange Online
+        ("40.104.0.0/15",     "microsoft",  "Microsoft"),
         ("157.240.0.0/16",    "meta",       "Meta"),
         ("31.13.24.0/21",     "meta",       "Meta"),
         ("129.134.0.0/16",    "meta",       "Meta"),