create() built the model through hydrate(), which skips #[Guarded]
properties on purpose: that is the right behaviour for an HTTP payload,
where a client must not set password_hash or a token. But create() is
called from trusted server code - a service, a seeder - and the guarded
value was silently dropped, so an account was inserted with an empty
password hash. The write succeeded and nothing failed loudly.
create() now re-applies guarded values after hydration, so every column
the caller passes is persisted. hydrate() keeps rejecting them, which is
what protects mass assignment.
Covered by CreateWithGuardedTest: one case for create() persisting the
hash, one asserting hydrate() still ignores it.