Provide setting for default client cache TTL setting for "external clients" #4926
Description
Is your feature request related to a problem? Please describe.
It is possible to adjust client and server timeouts for Steampipe CLI that allow to transparently use the CLI without any further interaction in such a way that Steampipe won't re-collect data from external APIs. This is possible for "external clients" as well, but only by using select from steampipe_internal.meta_cache_ttl({TTL_VALUE}) at the start of the session. This is fine for advanced users, but cumbersome and it would be great if this could be set via a configuration in Steampipe directly.
Describe the solution you'd like
Provide a setting that allows external client to make use of the same cache TTL set on the server.
Describe alternatives you've considered
Alternative is to use the CLI only, however a web frontend for Postgres is much more convenient, especially for not-so-technical users.