fix: writes with incorrect schema should fail

[hiltontj]

Summary of Changes

• Added a reproducer to replicate the scenario described in backtrace when writing different integer schema #25006
• Added a step in the write path to validate fields against the existing schema, to ensure that the fields being written have the same types as the existing schema
• Note: this incurs an extra check against each field in each line written when accept_partial=true; if this degrades performance, we could introduce a parameter that turns this check off, e.g., validate_schema, for users that don't want schema validation.

Example API Response

{
  "error":"partial write of line protocol occurred",
  "data":[
    {
      "original_line":"t0,t0_tag0=initTag t0_f0=0u 1715694000",
      "line_number":1,
      "error_message":"invalid field value in line protocol for field 't0_f0' on line 0: expected type i64, but got u64"
    },
    {
      "original_line":"t0,t0_tag0=initTag t0_f0=1u 1715694001",
      "line_number":2,
      "error_message":"invalid field value in line protocol for field 't0_f0' on line 1: expected type i64, but got u64"
    }
  ]
}

Closes #25006