store [nfc]: Make account-exists assumption explicit in some dartdocs

In particular:
  GlobalStore.loadPerAccount
  GlobalStore.doLoadPerAccount
  UpdateMachine.load

The first two already have an `assert` that the account exists, and
the third has a ! null-check. They're called in a chain from two
places, and we have the account in both: the initial account load
and the reload (GlobalStore._reloadPerAccount).

Author: chrisbobbe

lib/model/store.dart

@@ -145,7 +145,9 @@ abstract class GlobalStore extends ChangeNotifier {
     oldStore?.dispose();
   }
 
-  /// Load per-account data for the given account, unconditionally.
+  /// Load per-account data for the given account ID, unconditionally.
+  ///
+  /// The account for `accountId` must exist.
   ///
   /// This method should be called only by the implementation of [perAccount].
   /// Other callers interested in per-account data should use [perAccount]
@@ -189,7 +191,9 @@ abstract class GlobalStore extends ChangeNotifier {
     return store;
   }
 
-  /// Load per-account data for the given account, unconditionally.
+  /// Load per-account data for the given account ID, unconditionally.
+  ///
+  /// The account for `accountId` must exist.
   ///
   /// This method should be called only by [loadPerAccount].
   Future<PerAccountStore> doLoadPerAccount(int accountId);
@@ -909,7 +913,10 @@ class UpdateMachine {
     store.updateMachine = this;
   }
 
-  /// Load the user's data from the server, and start an event queue going.
+  /// Load data for the given account ID from the server,
+  /// and start an event queue going.
+  ///
+  /// The account for `accountId` must exist.
   ///
   /// In the future this might load an old snapshot from local storage first.
   static Future<UpdateMachine> load(GlobalStore globalStore, int accountId) async {