fix: move over to forked oclif

[Souvikns]

Description
Since oclif manifest command didn't have any way to get logs, this PR is installing a fork version of oclif and adding logs so that we can understand what is going on with the command.

Forked repo - https://github.com/Souvikns/oclif
adding logs - https://github.com/Souvikns/oclif/blob/main/src/commands/manifest.ts

[Souvikns]

it says https://github.com/asyncapi/cli/runs/5496164139?check_suite_focus=true#step:9:12 but we have rimraf

[Souvikns]

Clearly, the issue is with installing the library from GitHub. I found this maybe we can follow this, actions/setup-node#214. Maybe I am doing something wrong with setting up https://github.com/Souvikns/oclif do I also need to commit node_modules @derberg?

[derberg]

@Souvikns you definitely do not want to commit node_modules 😅 as it is just for testing really, can you just publish fork to your private npm? in linked issue folks say it helped to workaround the issue

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[Souvikns]

@derberg I released a new npm library with all the logs, once we are done with this I will delete that library.

[derberg]

btw, in a few days NPM will not allow you to delete the library. This is to prevent bad behavior in dependency manager. But yeah, not a problem to have it there. Might be you will need it in the future 😄

[Souvikns]

Now I will delete the tag and merge this PR.

[Souvikns]

/rtm

[asyncapi-bot]

🎉 This PR is included in version 0.16.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀