## Summary

- we don't need to index those
- it's dangerous with conversation rounds (different tool results with
same props but different types can lead to mapping exceptions) and with
tool config (same, different tool types can have different types for
their config props)

Because we can't just switch from `dynamic: true` to `dynamic: false`,
and because we don't want to rollout, we introduce a new `config` field
and are doing on-read / on-write migrations to access the legacy field
and move it to the new one

---------

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
(cherry picked from commit 1326704)