allow Summon to be excluded from the crown-time reset as a configurable rule

The recent change makes Dark Lord Summon reset the accumulated crown registration time when `ResetAccumulatedTimeAfterMove="1"` is enabled.

To be clear about what we are asking: we are not disputing the report, and we are not claiming the old behavior was correct. It was inconsistent with the rest of the option and the fix was the right call. What we would like to request is that the resulting rule — Summon not counting as a relocation for crown registration — be offered deliberately, as an option a server owner can switch on, rather than being unavailable entirely.

**Proposed configuration**

A separate flag under `CastleSiegeEvent`, evaluated only when `ResetAccumulatedTimeAfterMove="1"`:

```
ResetAccumulatedTimeAfterSummon = "1"
// 1 = Dark Lord Summon resets the accumulated crown registration time (current behavior, default)
// 0 = Summon is excluded from the reset; accumulated time is preserved
```

With the default set to `"1"`, no existing server is affected by the update in any way. Anyone who does not touch the configuration keeps exactly the behavior shipped in the fix. Only servers that deliberately set it to `"0"` opt into the alternative rule, with full awareness of what it does.

Since the reset now has a defined call site, we assume this amounts to a single configuration check at that point rather than any rework of the siege logic.

**Why we are asking**

Since the update went live we have received repeated requests from our players to make this possible again. Regardless of how the behavior originated, our community had built siege strategy around it and treats it as part of what a Dark Lord contributes to the event.

The practical impact is a balance one. A guild with fewer members cannot hold the Throne Room continuously against a guild with two or three times the roster — they lose the room, lose the accumulated time, and the siege is settled by headcount rather than by play. Being able to relocate their own Guild Master with Summon, keep the progress already earned, and return for the remainder gave outnumbered guilds a reason to contest the siege at all.

We understand completely that on other servers the same interaction is judged to be abuse, and the reset should apply there. That is precisely why we are asking for a switch rather than a change of default — one configuration line would let both communities run the ruleset they actually want, and neither has to lose anything.

We are happy to test the option on our server and report back before it goes into a general release.

Thank you for considering this.