fix(bindings): handle accessMode in runtime bindings with OPFS

[sumimakito]

This is an amazing project with many great works. Thank you

Context

During my recent usage with duckdb-wasm with the recent OPFS support done by @e1arikawa (Thank you for the cool work!), I encountered an issue where the file/directory handles were always created even when I opened the database with read-only options like:

db.open({
    path: 'opfs://not_yet_existing.db',
    accessMode: DuckDBAccessMode.READ_ONLY, // We should NOT create any files/directories
})

Summary

Going deeper, it seems we didn't handle the accessMode in helper functions like prepareFileHandles. Therefore, in this pull request, I tried to add the missing parameters to these functions as optional ones and added several test cases for open operations as such with different accessMode in OPFS.

[amiller-gh]

Five lines below this, where we call createSyncAccessHandle, we can pass a new optional mode to OPFS to further enforce the access mode: https://developer.mozilla.org/en-US/docs/Web/API/FileSystemFileHandle/createSyncAccessHandle#mode

If the access mode is passed to createSyncAccessHandle, it would allow read-only connections to be opened simultaneously (for example when using the same app in multiple tabs). A big win for duckdb-wasm + OPFS.

The option is only implemented in Chrome and Edge right now, but issues exist to implement in both Webkit and Firefox:
https://bugs.webkit.org/show_bug.cgi?id=283959
https://bugzilla.mozilla.org/show_bug.cgi?id=1949462

And tests have already been added to the Web Platform Tests dashboard:
https://wpt.fyi/results/fs/FileSystemFileHandle-sync-access-handle-lock-modes.https.tentative.worker.html?label=experimental&label=master&aligned

[amiller-gh]

Ah, just noticed you started a new PR for this! Will comment over there instead.