Plugin start timeout limited to 60s

[nmische]

Describe the bug
Plugin start timeout configuration longer than 60s not respected.

Steampipe version (steampipe -v)
v1.0.2

To reproduce
Configure several kubernetes connections (~20) to globally distributed clusters with many CRDs (~20). Configure plugin timeout to 5 mins:

plugin "kubernetes" {
  start_timeout = 300
}

Expected behavior
Steampipe should wait up to 300s (5min) for the kubernetes plugin to start.

Additional context
I had originally submitted a PR to allow for plugin start timeout configuration here. This allowed start timeout to be extended beyond the default 30s, however as additional kubernets connections were added to my configuration I noticed plugin startup times out at 60s, despite setting plugin start timeout to 300s.

[nmische]

I was able to trace this back to the hashicorp/go-plugin package, which has a default timeout of 60s.