Move ctrlBindings check into keyboardBindings function body to avoid global navigator reference

[iansan5653]

The reference to navigator at the top level makes combobox-nav unusable with SSR processes like React SSR. In particular, I am working on a component in PRC and cannot render the docs if combobox-nav is a dependency. For details, see the first list item in Gatsby's Debugging HTML Builds:

Some of your code references “browser globals” like window or document that aren’t available in Node.js. If this is your problem you should see an error above like “window is not defined”. To fix this, find the offending code and either a) check before calling the code if window is defined so the code doesn’t run while Gatsby is building (see code sample below) or b) if the code is in the render function of a React.js component, move that code into a componentDidMount lifecycle or into a useEffect hook, which ensures the code doesn’t run unless it’s in the browser.

When using this utility with React, it makes complete sense to construct the class inside a useEffect hook, so that part is already taken care of. However, because the reference to navigator is global, that doesn't fix the error.

We can easily fix this by just moving the navigator reference so it doesn't get called until (at minimum) the class gets constructed, so that's what I've done with this PR.

I considered putting the check inside the keyboardBindings function, but the performance impact of an additional regex check on every keyboard event felt unnecessarym, so I moved it into the class constructor and passed it as a parameter to keyboardBindings instead.

[theinterned]

I like this approach 👍

Just left a suggestion, but I think it's a debatable improvement (and I can see drawbacks of exposing something that previously was internal to the module) so take it or leave it.

[theinterned]

Thanks for making that change! Looks great

[iansan5653]

😕 I have no idea why the check is failing on MacOS

Edit: it was outdated dependencies