BTCMaps v2: drop hardcoded Status field on BtcMapResult

Per rollforsats feedback on PR #226 msg 82: the Status field on
BtcMapsBtcMapResult was a hardcoded 'submitted-for-review' constant
that didn't reflect anything the btcmap RPC actually returned.
submit_place's result envelope contains id / origin / external_id;
the queued-for-reviewer-workflow semantics are documented on the
BTC Map side, not signalled per-response. Carrying it on every
response was misleading.

PluginBuilder/APIModels/BtcMapsSubmitResponse.cs

@@ -19,10 +19,4 @@ public sealed class BtcMapsBtcMapResult
     public long? Id { get; set; }
     public string? Origin { get; set; }
     public string? ExternalId { get; set; }
-
-    // BTC Map treats import-RPC submissions as queued places that go through
-    // their reviewer workflow before appearing on the public directory map.
-    // A successful submit_place call means "submission accepted for review",
-    // not "place is live." Constant for clients to key off.
-    public string Status { get; set; } = "submitted-for-review";
 }