v0.1.6

• Add include_event_description config option to optionally include an
  event's description property inside the emitted logger.logEvent
  parameters map. This flag defaults to false to preserve existing
  behavior; enable it via analytics_gen.yaml (key: include_event_description).
  • The code generator now inserts a 'description' key for events that
    have a non-empty description when the flag is enabled.
  • The example config and README.md were updated to document this flag.
  • Unit tests assert that descriptions are properly included when enabled
    and omitted otherwise.
• Support interpolated placeholders in custom event_name strings
  • You can now include parameter placeholders in event_name using
    {parameter_name} and the code generator will replace them with
    Dart string interpolation in generated methods (for example,
    "Screen: {screen_name}" → "Screen: ${screenName}").
  • The raw event_name still appears unchanged in docs/exports so
    metadata remains stable across teams and exports.
  • If a placeholder doesn't match a parameter, it is preserved as-is
    (no silent mutations), so designs and engineers can detect typos
    or handle advanced use cases explicitly.