[api] Require field ids for schema fields, auto-assign them for parameter lists

[LuciferYang]

Purpose

close #9766

DataTypeJsonParser.parseDataField(JsonNode) passed a null counter into the private overload, so a field whose json carries no "id" hit fieldId.incrementAndGet() and threw a bare NullPointerException. That is reachable from create_function: ParameterUtils.parseDataFieldArray parses the user-written input_params / return_params json, and a parameter list like [{"name":"x","type":"INT"}] has no ids to carry.

The fix is not to make that entry auto-assign. parseDataField(JsonNode) is also how SchemaSerializer.deserialize reads a stored table schema field by field, and how the globally registered Jackson deserializer for DataField works. Table field ids drive projection and schema evolution, so quietly turning a missing id into 0 there would replace a loud failure with a wrong table. That entry stays strict; it now says so instead of throwing an NPE.

What changes instead is the caller that genuinely has an id-less list. The counter-taking overload becomes public, and parseDataFieldArray creates one counter for the whole array, so sibling fields get 0, 1, 2. Threading it per element would have handed every field id 0.

Behaviour per input, all of which previously threw an NPE as soon as one id was missing:

parameter list	before	after
no ids anywhere	NullPointerException	ids 0, 1, 2
every field has an id	works	unchanged
some fields have ids	NullPointerException	Partial field id is not allowed.
a table schema field with no id	NullPointerException	Field id is required but the field carries none.

Tests

DataTypeJsonParserTest covers the strict entry rejecting an id-less field, one counter handing out 0, 1, 2 across successive fields, an explicit id being kept, and the existing ROW path still numbering its fields sequentially.

ParameterUtilsTest covers parseDataFieldArray end to end: an id-less array becomes 0, 1, 2; explicit ids are preserved; a partially-id'd array is rejected with a message rather than an NPE.

Verified fail-on-base on JDK 11: with ParameterUtils reverted to master the id-less array test errors with Field id is required but the field carries none., and on master itself the same input throws NullPointerException at DataTypeJsonParser.parseDataField. paimon-api and paimon-common build clean with checkstyle and spotless.