Refactor ClientQuerySegmentWalker to fix fluent workflow violation

[a2l007]

Related to #5028
makeRunner inside ClientQuerySegmentWalker is designed to follow a fluent workflow but currently the usage of ResultLevelCachingQueryRunner does not completely adhere to this workflow.
Refactoring it to a fluent workflow is currently hindered by the nature of dependency between druid-processing and druid-server . FluentQueryRunnerBuilder which resides in druid-processing, cannot access ResultLevelCachingQueryRunner and most of the caching logic as they reside in druid-server.
Moving the ResultLevelCachingQueryRunner along with the caching logic into druid-processing is one approach towards making ClientQuerySegmentWalker#makeRunner cleaner but it may involve moving other related dependencies as well. Moving the FluentQueryRunner flow into druid-server is another approach which could be looked into.

[stale]

This issue has been marked as stale due to 280 days of inactivity. It will be closed in 2 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@druid.apache.org list. Thank you for your contributions.

[stale]

This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.