Introduce Support for CHECK/NO CHECK at Table and Column Level, and UPDATE/NO UPDATE at Column Level in Json Duality View

Problem / use case

Column level annotations CHECK/NO CHECK/UPDATE/NO UPDATE in JSON Duality views are not supported now.

Columb level annotations strengthens MySQL JSON Relational Duality Views by introducing fine-grained control over optimistic concurrency checks and column updates. It allows customers to decide which relational values protect a JSON document from conflicting changes and which fields may be updated through the duality view.

Proposed behavior

Column level annotations should be supported as part of this task for JSON duality views.

The new CHECK and NO CHECK annotations determine whether a table or column participates in ETAG calculation.
CHECK is the default at the table level. Untagged columns inherit their table's setting. A column-level annotation overrides the table setting.
Updating a NO CHECK field does not change the document's ETAG. This lets customers distinguish business-critical fields from values that should not trigger concurrency conflicts.

The new column-level UPDATE and NO UPDATE annotations control whether individual fields can be modified through the duality view.
Attempts to update a field whose effective setting is NO UPDATE are rejected. Primary-key columns cannot be marked as updatable, protecting relational identity and referential integrity.

Start by locating the existing JSON Duality View annotation implementation and its tests in MySQL Server. Use the proposed behavior as the acceptance criteria: support table- and column-level CHECK/NO CHECK and column-level UPDATE/NO UPDATE, including inheritance, ETAG effects, update rejection, and primary-key restrictions.