reorder create-svelte templates such that library is last * libskeleton was renamed to skeletonlib

[braebo]

• libskeleton was renamed to skeletonlib

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs

closes #6470

• This message body should clearly illustrate what problems it solves.

I've been seeing reports of users mistakenly choosing "Library skeleton project" because it's 2nd on the list in create-svelte, resulting in confusion. Moving it to be 3rd should help people avoid this mistake.

• Ideally, include a test that fails without this PR but passes with it.

Tests

• Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

• If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

[changeset-bot]

🦋 Changeset detected

Latest commit: f9f79d4

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

This PR includes changesets to release 1 package

Name	Type
create-svelte	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

[benmccann]

we could arguably come up with something a little more robust, but I'm happy enough with this for now. I'll leave it for the other maintainers in case they feel differently though

[Rich-Harris]

what ben said

[braebo]

Yea perhaps adding an "order" field to the template metadata file.