Maintain session info on new contexts

[timleslie]

This PR changes the behaviour of context.createContext in a fairly fundamental way: It now carries forwards the parameters that were used to create the original context object. This matches the behaviour we currently have implemented in the core createContext() function. This results in what is arguably the "expected" behaviour, if you do:

newContext = context.createContext({ skipAccessControl: true })

you will get a new context object which has the same session information as the original context. In the much less common case of this not being what you want you can always do:

newContext = context.createContext({ sessionContext: {}, skipAccessControl: true })

I think changing the behaviour of createContext is a nicer solution that the cloneContext function proposed in #4425.

[changeset-bot]

🦋 Changeset detected

Latest commit: 1ee0ee6

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

This PR includes changesets to release 8 packages

Name	Type
@keystone-next/keystone	Major
@keystone-next/example-auth	Patch
@keystone-next/app-basic	Patch
@keystone-next/example-ecommerce	Patch
@keystone-next/example-roles	Patch
@keystone-next/example-todo	Patch
@keystone-next/admin-ui	Patch
@keystone-next/auth	Major

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

[JedWatson]

OK, I'm convinced 👍