add ability to manage client lifecycles outside of VespaClients

[PrathamSoni]

there exists client overhead for creating vespasync/vespaasync client sessions at call time for say feed_iterable method. These can be created and managed at the app level to limit overhead. In addition, would enable improved connection pooling under the circumstance that client could be passed in as optional arg so that lifecycle of client is managed by end user.