exclude deploy artifacts from create-svelte

[Rich-Harris]

not a huge deal since we release via an action, but when i built this package locally it included the contents of .cloudflare. No harm in guarding against that happening during a manual release

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
• This message body should clearly illustrate what problems it solves.
• 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

Changesets

• If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts

[Conduitry]

Is this the .gitignore that ends up in users' projects, or is it used in deciding what gets published in the create-svelte package itself? I know there was something weird about npm publish renaming a file transparently.

If it's the latter, I'd probably prefer an explicit whitelist approach (with pkg.files) for what ends up in the package.

[Rich-Harris]

It's the latter. Whitelist is probably smarter, but would require some implementing, and I figured this quick fix is better than nothing in the meantime

[Conduitry]

👍 That's fair. Sounds good to me.