suggestion: BYO Deno.Kv instance

[MarkTiedemann]

Currently, this module always opens a new Deno.Kv instance.

deno_kv_oauth/lib/_kv.ts

Line 10 in 9dfc2a7

const kv = await Deno.openKv(path);

Would it make sense to add a kv property to the CreateHelperOptions when calling createHelpers?

Simply put, Bring Your Own KV. :)

Advantages:

• No need to open a second instance if one is already open
• You can choose which KVs to put the session data into if you're using multiple databases

[iuioiua]

We previously considered doing this and decided not to to make the data only accessible to the module. Let me ask a few more questions internally and get back to you.