feat(dynamodb): added endpoint filtering

[aryamohanan]

Enabled configuration to exclude specific dynamodb commands from tracing.

This can be configured via following ways:

Add the configuration to the agent's configuration.yaml file:

com.instana.tracing:
    ignore-endpoints: 
       dynamodb: 
         - query
         - listTables

Tracer configuration:

tracing: {
  ignoreEndpoints: {
    dynamodb: ['query']
  }
}

Using an Environment Variable:

INSTANA_IGNORE_ENDPOINTS=dynamodb:query,listTables;

With this setup, the tracer will ignore dynamodb commands such as QUERY or LISTTABLES, and any other dynamodb command can be added to the list for exclusion. This enhancement improves performance by reducing unnecessary tracing for specific dynamodb operations.

TODO

• Code and Test Implementation
• Public documentation https://github.ibm.com/instana/docs/pull/12356

ref INSTA-16323
ref #1448

[kirrg001]

In general: It could be that a span contains multiple data keys. But I have never seen a case where two instrumentation keys were present. I think only with the SDK 🤔
But I would ignore that for now I guess.

[kirrg001]

LGTM