feat: add sv kit as alias for svelte-kit command

[rChaoz]

(Partially?) closes #101

Adds a new alias command sv kit that calls svelte-kit, and documents it.

If all is good I'm happy to open a parallel PR to update SvelteKit's CLI page to either redirect to this or at least link it as the new CLI to use

[changeset-bot]

🦋 Changeset detected

Latest commit: 826050c

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

This PR includes changesets to release 1 package

Name	Type
sv	Minor

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

[benmccann]

I'm not sure this really makes sense. We're executing sv via npx, but SvelteKit is installed. We had at one point talked about having sv installed as well in which case additional aliases would make more sense. But we didn't end up going that direction. We should probably close the issue instead

[Conduitry]

Yeah, I'd be in favor of closing this and the corresponding issue. I don't think we want to have sv be a dependency of SvelteKit apps - there's no reason for them to have all the code needed to scaffold new projects or to migrate code. And if sv isn't a dependency, we don't want to encourage people to pull it down with npx just to have it call a dependency that they already have.

[rChaoz]

We're executing sv via npx, but SvelteKit is installed.

I had no idea, I always install sv instead, my check script even does sv check instead of svelte-check, I thought this was the intended direction; is this not why sv check exists?

If the intended direction is for sv to be just a tool for bootstrapping projects, I think this should be more clear, as currently it's defined as:

The command line interface (CLI), sv, is a toolkit for creating and maintaining Svelte applications.