Config file watcher issue in 0.12.2

[vhadianto]

Describe the bug

Steampipe Service 0.12.2 (might exist in earlier versions too) does not detect new and updated config file.

Steampipe version (steampipe -v)
Example: v0.12.2

To reproduce

1. Empty ~/.steampipe/config configuration and just leave 1 connection there. Let's say a Digital Ocean

2. Start Steampipe as a service.

3. Use pgcli/psql to connect and run the following query

select 
  ns.nspname as table_schema, 
  cls.relname as table_name,
  pg_catalog.obj_description(attr.attrelid) as table_description,
  attr.attname as column_name,
  pg_catalog.col_description(attr.attrelid, attr.attnum) as column_description,
  trim(leading '_' from tp.typname) as data_type
from 
  pg_catalog.pg_attribute as attr
  join pg_catalog.pg_class as cls on cls.oid = attr.attrelid
  join pg_catalog.pg_namespace as ns on ns.oid = cls.relnamespace
  join pg_catalog.pg_type as tp on tp.typelem = attr.atttypid
where
  ns.nspname !~ 'information_schema|pg_catalog|pg_temp|pg_toast|^pg_catalog|^pg_temp|^pg_toast|steampipe_command|public'
  and not attr.attisdropped 
  and attr.attnum > 0
order by 
  ns.nspname,
  cls.relname,
  attr.attnum;

This shows all the schema and the tables in Steampipe DB

4. Don't close pgcli, move a new connection config file to ~/.steampipe/config let's say it's Hackernews

5. Run the same query in step 3 - notice that the Hackernews schema and tables don't exist

6. Now in a new terminal run "steampipe query"

7. Back in pgcli run the same query in step 3 and notice that we now have the hackernews schema and tables