nvim-insx VS debugprint.nvim

I've implemented and published the [nvim-insx](https://github.com/hrsh7th/nvim-insx).

Folks, approximately a year ago I announced debugprint.nvim v0.1 here on r/neovim, a plugin to easily insert print-type statements into your code for debugging purposes; I'm happy to announce this since matured a lot and has reached v1.5.1. debugprint.nvim now supports 20 languages out-of-the-box, including virtually every popular modern language, can be extended to support more, and supports modern and classic NeoVim features, like dot-repeatability, normal/visual/operator-pending modes, Treesitter variable integration, and more.

Since I know there are quite a few fellow plugin authors on here (and plenty of users who may have an opinion too!), I wanted to ask a question / start a debate about the canonical way to customize keymappings for a NeoVim plugin. I maintain two plugins, debugprint.nvim and wrapping.nvim, both of which allow for users to customize the keymappings using the following kind of Lua-ish pseudo-code (let's call this Option 1):

Good work! I know I’m promoting my own work here (sorry!) but worth pointing out that my own https://github.com/andrewferrier/debugprint.nvim also already does this. Do you see any differences between the two? Are you interested in combining forces?

https://github.com/andrewferrier/debugprint.nvim ?

Of course, there are also keys like g? which technically have a purpose but almost everyone doesn't use. Which is why I map g? by default in my debugprint plugin ;)

For anyone already using debugprint.nvim, please be aware that I just pushed a breaking change to the default keybindings. This is for consistency, and I don't plan to make this kind of change regularly (!), but thought now was the time to do it before too many folks picked it up. Details here, including how to restore the old keys if you preferred them.