Support for defining project override configs in the project directory (instead of the nvim config directory)

[DaniloDjokic]

The PR encompasses a few things.

The main feature here is the ability to define the project override config in the project directory itself.
So, instead of having the navigate to the nvim configuration file and update the configuration of tmux-compile itself every time we want to add a new project, we simply define a 'tmux-compile.lua' file, either in the current working directory directly, or in subfolders '.nvim' or 'nvim'.

If the file is not defined the plugin still falls back looking for the project_override_config defined in the main configuration, and if it doesn't match the path there, it falls back to the file extension behavior.

Also, I've changed the vim.print commands to be vim.notify commands in order to better communicate to the user when they've made a configuration mistake.

And I've also added another command 'yazi'. Simillar to the 'lazygit' command, it opens the yazi TUI file manager in an overlay window.

P.S. The one conflict I've purposefully left unresolved as I would like your comment. I've modified the regex as it was not properly detecting .lua extensions but am not sure why it was not working in the first place.

Cheers

[karshPrime]

Much appreciate the PR!
I agree, updating the editor config to add/remove new projects isn't the best practice.