Initial suggestions for plugin release

Thank you @l-teles for the new plugin. The basic structure and results look good so far. While using the plugin, we did come up with a few suggestions based on our best practices:

README and docs/index.md files:
- For the token and secret, could you please use dummy values that are close to the actual format of the config arguments?
- Could you please explain the difference between DETECTIFY_API_SECRET and DETECTIFY_API_TOKEN_V3 config arguments?
```
# The access secret for API calls. Required.
# This can also be set via the `DETECTIFY_API_SECRET` environment variable.
# secret = "123"

# The access secret for v3 API calls. Required.
# This can also be set via the `DETECTIFY_API_TOKEN_V3` environment variable.
# secret = "123"
```
- Could you please modify the example query to use the following format:

  select
    to_char(created_at, 'YYYY-MM-DD HH24:MI:SS') as "Creation Date",
    date_part('day', NOW() - created_at) AS "Days Open",
    status as "Status",
    cvss_scores -> 'cvss_3_1' ->> 'severity' as "Severity",
    host as "Asset",
    title as "Title",
    case
      when source ->> 'value' = 'surface-monitoring' then 'EASM'
      else 'WebApp Scan'
    end as "Source",
    location as "URL",
    definition ->> 'description' as "Description"
from
  detectify_finding
where
  status not in ('accepted_risk','patched','false_positive');

Could you please update the Makefile as per https://github.com/turbot/steampipe-plugin-aws/blob/main/Makefile? This will also help local developers to build the plugin using the netgo package.

Overall the plugin looks great, the tables and the example queries are very compact.

Great work 🎉 !!

l-teles / steampipe-plugin-detectify

Initial suggestions for plugin release #3