Unify logic for metrics collection when any command is invoked

[peter-rr]

Add new methods to unify logic so metrics are collected when any CLI command is invoked. All this logic will be implemented in base.ts file and removed from the different command files.

[peter-rr]

@smoya Metrics are sent but the format of the action invoked is detected as undefined.
Working on the fix!

Also I need to remove the code corresponding to this metric in all the other commands.

[peter-rr]

@smoya
Some notes from last commit:

• Still figuring out the way to access some variables from the different command files, as you can see here.
• I'm considering to add any method which returns the appropriate rawDocument depending on the command executed. Or maybe this might be added inside callable function.
• The commented code from metrics recording on the different command files will be removed. Just keeping it for testing purposes by now.

[smoya]

I'm a bit confused about the reason you moved all the logic from each command to this big switch statement here.

As I see, this is going into a bit of a deep hole. Do you think we could roll back this (last changes) and just merge the PR so we can move forward and start collecting metrics? Then we could work on this later.

The extended side of this comment for future work:

We have what we would like to have ideally, a way of tracking, from the base.ts, that the command was executed and includes some metadata, if exists.
But I would say nothing about moving all the metadata collection logic to the base.ts file. This should stay in each command as it is the responsibility of each command to collect such metadata.

Instead of doing this, have you thought about the possibility of setting all this metadata into a property declared in the base.ts file but set on each command? I mean, something like this.metadata['success'] = true; but from the command. Then, base.ts could grab that metadata.

[peter-rr]

@smoya Last changes already rolled back so we can merge this PR and start collecting metrics.

[peter-rr]

@smoya What about this failing job?
Should we change something related to @asyncapi/cli dependency? 🤔
Same error at my local env when executing npm run build.

[smoya]

@smoya What about this failing job? Should we change something related to @asyncapi/cli dependency? 🤔 Same error at my local env when executing npm run build.

No, it is an general issue in the CLI repository. https://asyncapi.slack.com/archives/CQVJXFNQL/p1702289410144129

[smoya]

LGTM! 🚀🌔