[breaking] SSR config object

[JeanJPNM]

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 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 pnpx changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

Closes #1650 and is an alternative to #2529

[changeset-bot]

🦋 Changeset detected

Latest commit: 88b818a

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

This PR includes changesets to release 1 package

Name	Type
@sveltejs/kit	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

[dummdidumm]

If overridable is only there for the top level, then personally I like "never" more as an option. In an ideal world we would be able to do static analysis of the pages and don't need either of these options, but that probably has many edge cases and is very hard to implement, so I really like going with a third option for now.

[benmccann]

I prefer 'never' as well

[benmccann]

I'm going to close this in favor of the original PR since that seems to be the preference in order to keep the review queue clean