Custom Session Storage implementation and data

[sergiodxa]

Right now the Session Storage instance is created here

authkit-remix/src/cookie.ts

Lines 25 to 31 in edd45f9

	const { getSession, commitSession, destroySession } =
	createCookieSessionStorage({
	cookie: {
	name: cookieName,
	...cookieOptions,
	},
	});

And it's always using createCookieSessionStorage.

What happens if I want to use a different session storage? E.g. on Cloudflare I may want to use createWorkerKVSessionStorage, on Arc I could use createArcTableSessionStorage, and while createMemorySessionStorage and createFileSessionStorage are probably not recommended they're options and the memory one is specially useful on test environments.

I could also want to use createSessionStorage to create a new session storage where the session data is saved on the DB or Redis or anywhere else.

Additionally, I may want to use the session to store more data that my app needs, right now I can't import the session storage to access it myself.

I think the library should expect a SessionStorage compatible object and use that internally, giving me control of what session storage I choose to use and how I use it.

[PaulAsjes]

This (and the other issues you opened) is great feedback, thanks! We're going to action all of these in the next few weeks.