feat: refactor state, store it securely

[nirinchev]

Uses @napi-rs/keyring to store the credentials from the state in the OS secure storage location.

Additionally, reactors State to have a persistent field which gets stored and session field where we can add global state that should not persist across launches. For now, this is only the NodeDriverServiceProvider, which was previously in a now-deleted MongoDBToolState.

The node library we're using is a wrapper around https://github.com/open-source-cooperative/keyring-rs, which is a rust-based implementation wrapping the native credential stores for most desktop operating systems.

Fixes #20

[gagik]

Could be good to turn a State into a class with an enclosed entry if we ever want to support multiple credentials but for our current scope this looks good

[fmenezes]

LGTM, personally I would separate session and credentials and remove state from the picture

[nirinchev]

@gagik @fmenezes I used your feedback as inspiration and tried to do something in the middle 😅 I'm keeping the credentials and the rest of the state combined, but they're now encapsulated in a class responsible for saving/loading of data. I decided to keep them together until we decide what we want to do with the auth flows and whether we want to persist data at all, but should be fairly trivial to rip out if necessary.

[blva]

nice, LGTM 🚀