chore: remove chainhook subcommands

[tippenein]

closes #1308

(also fixes #1310 links)

[sabbyanandan]

@tippenein: 💥!

More importantly, I love this:

[codecov]

Codecov Report

Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (4bfe976) 40.44% compared to head (b6347ae) 40.64%.

Files	Patch %	Lines
components/clarinet-cli/src/frontend/cli.rs	0.00%	3 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #1328      +/-   ##
===========================================
+ Coverage    40.44%   40.64%   +0.20%     
===========================================
  Files           87       86       -1     
  Lines        31766    31591     -175     
===========================================
- Hits         12847    12841       -6     
+ Misses       18919    18750     -169     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[hugocaillard]

Thanks @tippenein. And happy new year! 🎉

What do you think about printing a message explaining that clarinet chainhook is no longer available (because it wasn't maintained)? And maybe suggest alternatives? (cc @MicaiahReid)

No hurry on this, I think we'll hold the PR for after the next release (2.2.0)

[tippenein]

hey @hugocaillard
Yeah that sounds fine by me 👌

[MicaiahReid]

Hey @tippenein, thanks for the PR!

I had some time to give this one some thought, and I think we only actually want part of this change.

Clarinet had the clarinet chainhook new command that would generate chainhooks that are no longer compatible with the actual Chainhook tool. Now that Chainhook is a standalone tool, we don't need to have the generation of these files inside of Clarinet.

However, Clarinet still finds a user's chainhooks in their working directory and automatically registers them with their devnet, which is a really helpful feature that we actually just released a guide on.

Would you be able to revert the changes that remove chainhook from the devnet?

[tippenein]

@MicaiahReid thanks for the feedback. So, we're essentially only deprecating the chainhook new ?

This is what it looks like currently:

[MicaiahReid]

So, we're essentially only deprecating the chainhook new

@tippenein Apologies for the mixed messaging here. We can also deprecate chainhook check and chainhook deploy.
If, after deprecating those, you find some helper functions in the stacks-network component that are no longer used, those can be removed (for example, I think we'll be able to do away with the check_chainhooks function).

What will need to remain is all code that is used by the stacks-network to load the chainhooks into a devnet.

[tippenein]

@MicaiahReid Yea that makes total sense. It should be good now 👍 lmk

[MicaiahReid]

Looks good, thanks @tippenein!

[hugocaillard]

Thanks @tippenein!
I'm merging now