Aftermerge fixes.

Only return the error if field->store produced errors, not warnings.

Followup part#2: allocate the List object on the right mem-root, too.

Followup to review input address commit: pass the new parameter type
to find_field_in_table_ref().

MDEV-25420 JSON_TABLE: ASAN heap-buffer-overflow in Protocol::net_store_data or consequent failur es.

fixed changed.

Address review input: switch Name_resolution_context::ignored_tables from
table_map to a list of TABLE_LIST objects. The rationale is that table
bits may be changed due to query rewrites, etc, which may potentially
require updating ignored_tables.

MDEV-25420 JSON_TABLE: ASAN heap-buffer-overflow in Protocol::net_store_data or consequent failures.

error in the patch fixed.

Do not adapt to the argument charset anymore. Just use the utf8mb4 as
the default cherset.

MDEV-25420 JSON_TABLE: ASAN heap-buffer-overflow in Protocol::net_store_data or consequent failures.

Create_tmp_table::add_field didn't consider BIT type field for
null_counter.

We need to update default values if we change the column's charsets.

If a field is not in the read set - read it in the local buffer anyway to check for errors.

When doing name resolution, do the same what WHERE/ON clauses do:
they don't count in select_lex->non_agg_field_used().

atch to get rid of duplicating code of the Create_tmp_table.

MDEV-25259 JSON_TABLE: Illegal mix of collations upon executing query with combination of charsets via view.

now the ::print printed too much. Limit it for fields with no CHARSET
possible.

MDEV-25259 JSON_TABLE: Illegal mix of collations upon executing query with combination of charsets via view.

The ::print method didn't print the explicitly specified charset.

test crashing after any_db assinged nonzero lenght fixed.

test crashing after any_db assinged nonzero lenght fixed.

Table_function_json_table::m_dep_tables attempts to cache the value of
m_json->used_tables(), poorly. Remove the cache and use the value
directly.

The query used a subquery of this form:

SELECT ...
WHERE
   EXISTS( SELECT ...
           FROM JSON_TABLE(outer_ref, ..) as JT
           WHERE trivial_correlation_cond)

EXISTS-to-IN conversion code was unable to see that the subquery will
still be correlated after the trivial_correlation is removed, which
eventually caused a crash due to inability to construct a query plan.

Fixed by making Item_subselect::walk() also walk arguments of Table
Functions.

Use a function instead of lambda

(TODO: squash this with previous patch for MDEV-25346)

add_table_to_list - remove the table_function argument.

mysql_derived_prepare() sets Name_resolution_context::outer_context=NULL
for the WHERE clause's context.
Do the same for all ON expressions, too.

Add testcase

Followup: also handle NATURAL JOIN, extend the new approach with
Name_resolution_context::ignored_tables

tests updated.

- Address review input. No functional changes.

Post-rebase fix, JSON_TABLE touched the parser.

(Also fixes MDEV-25254).
Re-work Name Resolution for the argument of JSON_TABLE(json_doc, ....)
function. The json_doc argument can refer to other tables, but it can
only refer to the tables that precede[*] the JSON_TABLE(...) call.

[*] - For queries with RIGHT JOINs, the "preceding" is determined after
the query is normalized by converting RIGHT JOIN into left one.

The implementation is as follows:
- Table function arguments use their own Name_resolution_context.

- The Name_resolution_context now has a bitmap of tables that should be
  ignored when searching for a field.

- get_disallowed_table_deps() walks the TABLE_LIST::nested_join tree
  and computes a bitmap of tables that do not "precede" the given
  JSON_TABLE(...) invocation  (according the above definition of
  "preceding").

should not abort on field::set().

More informative messages added.
Do not issue additional messages if already handled.

feature_json variable incremented.

Field reset added.

syntax fixed.

calling members of NULL object crashes on some platforms.

No plugin for the JSON_TABLE so get the storage type name directly.