refactor recommendation packages

[felixhaeberle]

• fix SHERL-2
• fix SHERL-58
• fix SHERL-83

---

In his PR, we

• renamed cross-sell-X packages to recommend-X to be more descriptive
• refactor recommendation view to Sherlock VS Code extension
• introduce new shouldRecommend function to @inlang/recommend-sherlock & @inlang/recommend-ninja

cc @NiklasBuchfink needs your review after I'm done.

[changeset-bot]

🦋 Changeset detected

Latest commit: 5996c15

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 17 packages

Name	Type
@inlang/recommend-sherlock	Minor
@inlang/recommend-ninja	Minor
@inlang/paraglide-js	Minor
vs-code-extension	Minor
@inlang/paraglide-next	Patch
@inlang/paraglide-sveltekit	Patch
@inlang/paraglide-unplugin	Patch
@inlang/paraglide-js-e2e	Patch
@inlang/paraglide-sveltekit-example	Patch
@inlang/paraglide-next-example-app	Patch
@inlang/paraglide-next-example-pages	Patch
@inlang/paraglide-next-example-turbo	Patch
@inlang/paraglide-next-e2e	Patch
@inlang/paraglide-rollup	Patch
@inlang/paraglide-vite	Patch
@inlang/paraglide-webpack	Patch
@inlang/paraglide-astro	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[felixhaeberle]

@LorisSigrist | @NiklasBuchfink, please review this for your apps and see if everything regarding the recommendations is working correctly?

@LorisSigrist I went for a patch change, but we should potentially do a minor one. Furthermore, I changed the package names. If I remember correctly, you already did this with the paraglide packages. Do you know if I have to look after something regarding npm publishing?

[LorisSigrist]

We should probably do a "minor" patch for packages using it, as "patch" changes are usually not taken as seriously by module-resolvers.

As for the renaming: I don't think anything is going to break, but i would mark the old packages as depreciated on npm via the npm cli