Stop sending `{}` to the `/api/auth/login` endpoint when the login form hasn't been touched.

Steps to reproduce:

**Note**: You will need to watch the traffic in a DOM inspector; this has no user-observable symptoms because there's presently no error reporting for the login form.

1. In a new private tab, visit the `/login` page of a Pilcrow instance.
2. **Without touching the username or password fields**, click `sign in`.

The client _should_ send a request to `/api/auth/login` with the following payload:

```json
{
  "name": "",
  "password": ""
}
```

However, it instead sends an empty payload, leading to a 422 Unprocessable Content response as the request is missing required fields. Subsequent requests, or any request after the user enters data in the input fields, are correctly serialized.

Merges login-form-nulls into main.

0 files changed, 0 insertions, 0 deletions