We should introduce more assert ThreadPool.assertCurrentThreadPool(...) in various esql components such as planner, analyzer and executor (or essentially any component directly or indirectly used from EsqlSession) to ensure they are running on correct thread pools.
This is required to ensure we do not hit or introduce unexpected bottlenecks due to incorrect thread pool usage.

Based on the findings we might need to move some of the workload to different thread pools or even introduce a new ones.