Don't double-process ResultMetaData for BufferedColumnResultProxy

Don't double-process ResultMetaData for BufferedColumnResultProxy

Fixed a bug in the result proxy used mainly by Oracle when binary and
other LOB types are in play, such that when query / statement caching
were used, the type-level result processors, notably that required by
the binary type itself but also any other processor, would become lost
after the first run of the statement due to it being removed from the
cached result metadata.

Change-Id: I751940866cffb4f48de46edc8137482eab59790c
Fixes: #3699
(cherry picked from commit f3bc60bdd809235cbeb3f414717ac0e273269cf9)