Feat: add typo suggestions to MODEL block field errors

[treysp]

Before

  Invalid extra fields {'descriptions', 'dialects'} in the model definition

  Invalid extra fields {'batch_sizes'} in the model kind 'INCREMENTAL_BY_TIME_RANGE'

After

  Invalid field names present in the MODEL block: 'dialects', 'descriptions'
  
    - dialects: Did you mean 'dialect'?
    - descriptions: Did you mean 'description'?

  Invalid field name present in the MODEL block 'kind INCREMENTAL_BY_TIME_RANGE' field: 'batch_sizes'. Did you mean 'batch_size'?

[benfdking]

not important: This looks great to me and is a lovely bit of kit!

@izeigerman this is an example of the thing I talked about on Tuesday when I was saying building with sympathy for the "LSP"

To me, this is a perfect example of something that could be a diagnostic, e.g., if this were a structured error, we could

1. Highlight it in line, e.g., under the misspelled word
2. Suggest a code action that could correct the mistyped word to the 'close_match'

Actually even more than just for the LSP if you printed it correctly, you could print a link to the file with the right code line that IDE's would pick up as a link to the right file and place.

[izeigerman]

I hear you. Though, I don't believe all the relevant information is available here—for example, the position of the field in the code. So Trey wouldn't be able to express this sympathy in the PR even if he wanted to, since he doesn't have access to the original source, only the Pydantic model object.