RA vtable functions need to take pool arguments.

The RA vtable definition cripples proper pool management by requiring
that RA implementations use the one pool available to them -- the
session pool.  While many RA functions aren't called in loops very
often, the possibility to do so exists, and therefore our API needs to
include 'pool' arguments for the vtable functions so that callers
using loops can minimize the memory usage.