This method was implemented when we didn't have query available for removeLiquidityRecovery, but now we do and it's already being handled inside the default Remove Liquidity query, so we can remove it as duplicate.

Note: v2 would still need the custom implementation of query for remove liquidity recovery, as there's no actual query available on vault (v2). But in any case, we should consider a refactor where queryRemoveLiquidityRecovery custom implementation is moved to inside query to make sure both v2 and v3 share the same external interface.