fix: solve optimize command issue when sending data to New Relic

[peter-rr]

Description
Solving issue from optimize command when sending data to New Relic servers.
Basically, action.finished metric is not sent to NR servers probably because of the format accepted by New Relic API.

[peter-rr]

The optimizations array is now displayed as an object when testing the command locally, i.e. the sink used is StdOut. However, the metric action.finished is not sent to New Relic servers yet.
cc @smoya

[peter-rr]

The metric action.finished is now sent to New Relic servers. This is how optimizations property looks like after being converted to JSON format:

cc @smoya

[smoya]

The metric action.finished is now sent to New Relic servers. This is how optimizations property looks like after being converted to JSON format:

cc @smoya

The value in optimizations you are sending is a plain string instead of an array. As per NR docs, attributes can only contain numbers, strings or booleans.

In order to allow filtering/querying/grouping/etc by those attributes, you will need to send them separated in different attributes. For example:

{
  "optimization_remove-components":  true,
  "optimization_reuse-components": true,
  "optimization_move-to-components": true,
  "success": true,
  "asyncapi_blablabla": "etc etc etc"
}

[peter-rr]

Metadata attributes already adapted to NR requirements 👍
Now working on reducing the cognitive complexity introduced with this last commit.

[peter-rr]

Working on the test failing:
https://github.com/smoya/cli/actions/runs/7814302325/job/21315288099?pr=13

[peter-rr]

Cognitive complexity issue solved and failing test fixed with this commit: 737f3ee

[peter-rr]

@smoya
Ready for review 💪

[peter-rr]

Refactor applied and --optimization flag working correctly now. Ready to merge 🚀