Improve error message when auto-creating timeseries with null value

[jt2594838]

Description

When an insert contains a null value for a non-existing timeseries, schema auto-creation skips that timeseries because its data type cannot be inferred. The subsequent error previously only reported that the path did not exist.

This PR:

• adds dedicated English and Chinese error messages explaining both that the timeseries does not exist and that its data type cannot be inferred from the null value;
• uses the dedicated error for missing measurements whose inferred data type is null, while preserving the existing error for other missing paths;
• updates IoTDBInsertMultiRowIT#testInsertAlignedSeriesAutoCreate to verify the JDBC error message.

Tests

• mvn test-compile -DskipTests
• mvn test-compile -P with-zh-locale -DskipTests
• IoTDBInsertMultiRowIT#testInsertAlignedSeriesAutoCreate: 1 test run, 0 failures, 0 errors

---

This PR has:

• been self-reviewed.
• added integration tests.
• been tested in a test IoTDB cluster.

---

Key changed/added classes (or packages if there are too many classes) in this PR

• PathNotExistException
• InsertBaseStatement
• InsertRowStatement
• DataNodeSchemaMessages
• IoTDBInsertMultiRowIT