fix(python): added debugpy path auto-resolution using mason-registry

[BillKills974]

Mason installs debugpy in a venv in $HOME/.local/share/$NVIM_APPNAME/mason/packages/debugpy/ .
This fixes a bug where DAP would not find debugpy (ModuleNotFoundError : no module named "debugpy") and would not start debugging.
The replaced code would only work if you just installed debugpy or running :DapInstall python and use DAP without exiting nvim, or if you had debugpy installed system-wide (via pip) and not using a venv. It would fail upon new nvim runs.

[github-actions]

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

• If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

• If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

• Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

• README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

• Proper usage of opts table rather than setting things up with the config function.

[mehalter]

Thanks for this! I think we can also go ahead and extend the config function here to pass the opts into the setup call as the second argument. This will allow users to easily use the opts key in lazy to override the options in the setup without losing the mason addition

[mehalter]

Perfect! I will go ahead and merge this :) Thanks so much! I think I also have some other ideas to improve this integration with mason, so I'll make a follow up PR as well :)