Improve sink/integration developer experience about dna HOT 3 CLOSED

• How do you want to read the JS/TS file ? Deno ?
• I suggest we avoid nesting, I'd prefer the config to look like

export const config: Configuration<StarknetFilter, PostgresSink> = {
  type: 'starknet',
  streamUrl: 'https://mainnet.starknet.a5a.ch',
  bearerToken: Deno.env.get('DNA_TOKEN'),
  // other options
  startingCursor: 123_456,
  filter: Filter().withHeader({ weak: false }).toObject(),
  sinkType: 'postgres',
  sinkOptions: {
      connectionUrl: 'postgres://....',
    }
  }
}

• --stream.bearer-token=xxx this looks not so standard to me, I'd prefer it to be just --bearer-token or --stream-bearer-token
• Why do we need to prefix the sink options with --<sink.type> ? it looks cumbersome to me

from dna.

• Yes, the javascript runtime is Deno. The ts -> js transpilation is provided by a crate that leverages swc
• I agree it looks better without nesting.
• The dot in the name is used by some tool (grafana etc, geth) to mimic the nesting in the config. If we remove nesting it's not needed anymore.
• The prefix is needed to avoid clashing when using env variables. So let's say I need to use a bearer token to authenticate with my db, then it's in the DB_BEARER_TOKEN env variable and doesn't clash with the stream bearer token.

from dna.

This was done in #188

from dna.