Keep an edited filter rule where it was

Renaming or editing a Sieve rule moved it to the bottom of the list, and
in Sieve the order is the order the rules run in, so mail started being
filed by a different rule than before. Putting it back took a click per
place moved.

Two things did it. saveAndApply always appended the rule it was given —
right for a rule created from a message, wrong for one being edited. And
the "Also apply to existing messages" tick defaulted to on wherever it
was offered, so every edit in Settings went down that path, including a
plain rename.

The rule now keeps its seat: a shared upsertRule replaces by id in place
and only appends what is genuinely new. The tick defaults to on only in
"Filter messages like this…", where applying it is the point, and the
toast no longer calls an edited rule "created".

Fixes #24

web/src/views/settings/RuleDialog.tsx

@@ -13,13 +13,15 @@ export interface RuleDialogProps {
   onSave: (r: SieveRule, applyNow: boolean) => void;
   /** When set, offers "Also apply to existing messages in <folder>". */
   applyMailbox?: { id: Id; name: string } | null;
+  /** Ticks that offer by default. Off unless applying is the point of the dialog. */
+  applyByDefault?: boolean;
   title?: string;
   saveLabel?: string;
 }
 
-export function RuleDialog({ rule, onClose, onSave, applyMailbox, title, saveLabel }: RuleDialogProps) {
+export function RuleDialog({ rule, onClose, onSave, applyMailbox, applyByDefault, title, saveLabel }: RuleDialogProps) {
   const [r, setR] = useState<SieveRule>(rule);
-  const [applyNow, setApplyNow] = useState(Boolean(applyMailbox));
+  const [applyNow, setApplyNow] = useState(Boolean(applyMailbox && applyByDefault));
   const mailboxes = useMail((s) => s.mailboxes);
   const mailboxPath = useMail((s) => s.mailboxPath);
   const folders = useMemo(() => Object.values(mailboxes).map((m) => ({ id: m.id, path: mailboxPath(m.id) })).sort((a, b) => a.path.localeCompare(b.path)), [mailboxes, mailboxPath]);