Identity created with uppercase letter in email cannot be PATCHed

[sloosch]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• This issue affects my Ory Network project.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Describe the bug

Trying to PATCH the verifiable_addresses verified and/or status flag is not possible if the identity was created with an uppercase letter in the email.

Reproducing the bug

• Use an identity schema with a trait having an email and verification via email enabled.
• Create a new identity with an email containing a uppercase letter e.g. Test@test.com
• Try to change the verified status of the newly created identity via PATCH using the admin api of kratos: e.g. kratos running locally with exposed admin port 4434 curl -v -X PATCH --data '@./patch.json' -H 'Content-Type: application/json' http://localhost:4434/admin/identities/<the-identity-id>'
  where patch.json does contain the patch operation:

[
  {
        "op": "replace",
        "path": "/verifiable_addresses/0/verified",
        "value": true
  }
]

• In the response observe that verifiable_addresses was not updated and does contain a null-id and null-created-at date:

{"id":"c9d94f94-fa72-418f-a5b7-b78702377a19","credentials":{"password":{"type":"password","identifiers":["test@test.com"],"version":0,"created_at":"2023-03-24T10:01:28.041839Z","updated_at":"2023-03-24T10:23:38.077894Z"}},"schema_id":"default","schema_url":"http://127.0.0.1:4433/schemas/ZGVmYXVsdA","state":"active","state_changed_at":"2023-03-24T10:01:28.039621074Z","traits":{"email":"Test@test.com","name":{"first":"Test","last":"Test"}},"verifiable_addresses":[{"id":"00000000-0000-0000-0000-000000000000","value":"test@test.com","verified":false,"via":"email","status":"pending","created_at":"0001-01-01T00:00:00Z","updated_at":"0001-01-01T00:00:00Z"}],"recovery_addresses":[{"id":"00000000-0000-0000-0000-000000000000","value":"test@test.com","via":"email","created_at":"0001-01-01T00:00:00Z","updated_at":"0001-01-01T00:00:00Z"}],"metadata_public":null,"created_at":"2023-03-24T10:01:28.04083Z","updated_at":"2023-03-24T10:01:28.04083Z"}

• Observe the verifiable_addresses was really not updated by issuing a GET request: curl -v -X GET http://localhost:4434/admin/identities/<the-identity-id>'
• Repeat the above steps with an email address containing only lowercase letters and the PATCH can be executed

Relevant log output

No response

Relevant configuration

Identity schema

{
    "$id": "https://schemas.ory.sh/presets/kratos/quickstart/email-password/identity.schema.json",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "title": "Person",
    "type": "object",
    "properties": {
      "traits": {
        "type": "object",
        "properties": {
          "email": {
            "type": "string",
            "format": "email",
            "title": "E-Mail",
            "minLength": 3,
            "ory.sh/kratos": {
              "credentials": {
                "password": {
                  "identifier": true
                }
              },
              "verification": {
                "via": "email"
              },
              "recovery": {
                "via": "email"
              }
            }
          },
          "name": {
            "type": "object",
            "properties": {
              "first": {
                "title": "First Name",
                "type": "string"
              },
              "last": {
                "title": "Last Name",
                "type": "string"
              }
            }
          }
        },
        "required": [
          "email"
        ],
        "additionalProperties": false
      }
    }
  }

### Version

0.11.1

### On which operating system are you observing this issue?

Linux

### In which environment are you deploying?

Docker

### Additional Context

_No response_

[DASPRiD]

Good to know. I assume a workaround for now might be to lowercase all email addresses on registration through the front-end.