bug: notify field in config not working

[danielreis1]

Did you check docs and existing issues?

• I have read all the which-key.nvim docs
• I have updated the plugin to the latest version before submitting this issue
• I have searched the existing issues of which-key.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

0.10

Operating system/version

windows 10, using alacrity and wsl

Describe the bug

I expected setting the notify to false and not getting notification messages

the most basic config would have something like this at the start:

problem with this is when I start nvim it triggers a warning, triggering this warning makes it such that other plugins that start windows at startup break, because the warning shuts down the picker windows, please fix and make it such that the warnings are optionally for god's sake
the suggestions to fix these warnings are all broken as well for some reason
here are the problematic nvim startup warnings

Steps To Reproduce

1. set notify to false
2. add problematic config, whatever causes a warning

Expected Behavior

I expected setting the notify to false and not getting notification messages

here are the problematic nvim startup warnings

Health

No response

Log

No response

Repro

vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    { "folke/which-key.nvim", opts = {} },
    -- add any other plugins here
  },
})

[folke]

You're calling register BEFORE calling setup