0.6.2 — a profile row belongs to its account, by foreign key

A new migration (20260917200000_users_follow_auth_users.sql) gives public.users.id a foreign key to auth.users(id) with ON DELETE CASCADE, and drops the on_auth_user_deleted trigger and handle_deleted_user() that deleted the row by hand. The id of a profile row IS the account's id, so the row is a child of the account and the database can be told so directly: it cannot be forgotten the way a trigger can, it also refuses a profile row for an account that does not exist, and it is one mechanism instead of two. Deleting an account still cascades on to devices, and delete_own_account() is unchanged.

The migration clears any profile rows whose account is already gone before adding the key, so it applies to a database that was restored or written to by hand. Package version stays 0.0.1 by design.