SQLBatchRequestResultSet needs design optimization

- why SQLBatchRequestResultSet needs a brpc:Controller?
- SQLBatchRequestResultSet can get common view & non common view directly. We don't need to get all cols, then check if constant, push to common or non common data resp. It's meaningless decode and encode.
- SQLBatchRequestResultSet::GetSchema doesn't have the propery of constance. But we can't get common idx from SQLBatchRequestResultSet.

Examine SQLBatchRequestResultSet class in the codebase to understand its current design and usage of brpc::Controller. Identify where common and non-common views are handled and how schema retrieval works. Look for existing tests related to result sets to understand expected behavior after optimization.

Written by the indexing model from the issue text.