DbEntityValidationException logs include lazy loaded navigation properties

[DavidJohnWilliams]

Describe the bug

When a DbEntityValidationException is thrown the EntityValidationErrors.Entry.Entity is logged including all navigation properties.

Steps to reproduce

1. Enrich.WithExceptionDetails
2. Cause a 'DbEntityValidationException'
3. Entire entity graph is included in log (including navigation properties which query the database)

Here is a basic app for repo:
Serilog.Exceptions.EntityFramework.zip

Expected behaviour

Entities are not destructured

[DavidJohnWilliams]

I would like to contribute some kind of fix for this, but first would like understand why it is happening. Especially given that the primary example in the readme for this repo is for this exact error scenario. In the sample json Entry is null. However for my sample I get the following (note that room was lazy loaded):

Log JSON

{
  "@t": "2025-05-23T16:26:55.0057478Z",
  "@mt": "Error",
  "@l": "Error",
  "@x": "System.Data.Entity.Validation.DbEntityValidationException: Validation failed for one or more entities. See 'EntityValidationErrors' property for more details.\r\n   at System.Data.Entity.Internal.InternalContext.SaveChanges()\r\n   at System.Data.Entity.Internal.LazyInternalContext.SaveChanges()\r\n   at System.Data.Entity.DbContext.SaveChanges()\r\n   at Program.<Main>$(String[] args) in D:\\Repos\\Experiments\\Serilog.Exceptions.EntityFramework\\Serilog.Exceptions.EntityFramework\\Program.cs:line 19",
  "ExceptionDetail": {
    "HResult": -2146232032,
    "Message": "Validation failed for one or more entities. See 'EntityValidationErrors' property for more details.",
    "Source": "EntityFramework",
    "TargetSite": "Int32 SaveChanges()",
    "EntityValidationErrors": [
      {
        "Entry": {
          "Entity": {
            "Id": 1,
            "Name": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
            "RoomId": 2,
            "Room": { "Id": 2, "Name": "Maths Class" } <-- Lazy loaded
          },
          "State": "Modified",
          "CurrentValues": { "PropertyNames": ["Id", "Name", "RoomId"] },
          "OriginalValues": { "PropertyNames": ["Id", "Name", "RoomId"] }
        },
        "ValidationErrors": [
          {
            "PropertyName": "Name",
            "ErrorMessage": "The field Name must be a string or array type with a maximum length of '50'."
          }
        ],
        "IsValid": false
      }
    ],
    "Type": "System.Data.Entity.Validation.DbEntityValidationException"
  }
}

There was a similar issue reported for EF Core, however this is EF6.

So far as I can tell from looking over the code, there is no specific destructurer for this kind of exception (make sense as it is in EF assembly) meaning it will default to the ReflectionBasedDestructurer. In which case it should always have accessed all the navigation properties as a result?

If anyone can shed any light on this I would be very grateful.