feat: support stacks.js v7

[hugocaillard]

Description

Update the clarinet js sdk to use stacks.js 7 and vitest 2

This PR introduces breaking changes in the sdk, the release strategy is tbd, either:

• release the clarinet sdk as 3.x but decouple it from clarinet versionning (and keep the cli as 2.x), would make sense but bring a bit of confusion
• break semver an release as 2.x, not ideal

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
components/clarinet-cli/src/generate/project.rs	0.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[pradel]

release the clarinet sdk as 3.x but decouple it from clarinet versionning (and keep the cli as 2.x), would make sense but bring a bit of confusion

Making clarinet and the SDK have the same version is nice, what's the issue with releasing this as clarinet v3?

[hugocaillard]

Making clarinet and the SDK have the same version is nice, what's the issue with releasing this as clarinet v3?

Some people can expext major updates or new features from a new major version.
And for developers to upgrade (and adapt to breaking changes), they have to find some value in it.

But we are doing it. Here is (almost) everything that will be included in 3.0: #1672
cc @pradel

[janniks]

Looks great! 👏 Functional, clean!