Granual plugin management for doomnvim, allowing the user to enable either specific plugins or groups of plugins

For the dev branch, when doing a fresh install, on the first launch doomnvim will throw a lot of error messages because it loads the plugins and their configs before vim-plug could download them.

This only happens once and does not have any impact for doomnvim.

Need to fix it by lazy loading the configuration files

Permanent colorscheme edition with dashboard-nvim

Allow the user to choose doomnvim or doom-emacs keybindings

Allow installation of doomnvim on Windows and OSX

Allow user to move buffer to a new tab

A lot of functions are bloated and split into different files. Grouping them and cleaning the messy code will make developement easier.

Configuration options:

• enable/disable folds

Maybe get the installer to do the first configuration file

The LayoutToggle() function might move the NERDTree buffer and the terminal buffer

On a fresh install, the dev branch will not work since plugins are not downloaded on first start

When using custom plugins with g:doomnvim_custom_plugins, doomnvim will remove them whenever there is an update

Limit usage of vimscript in order to use lua with neovim

Migrate from vim-clap to telescope.nvim

Add correct syntax for doomnvim.log

Describe the bug
The reopening is not necessarily done on the last file (penultimate folder/workspace).

To Reproduce
Steps to reproduce the behavior:

1. Open a folder
2. Select a file
3. Quit Vim
4. Reopen Vim
   The error frequency is quite random.

Expected behavior
Reopen on the last workspace/file. Otherwise an empty workspace

Desktop (please complete the following information):

• OS: Manjaro (Kernel Linux 5.8.16)
• Console: Konsole (Version 20.08.1)

On some terminals the use of floatterm leaves some artifact that must be closed manually

Custom packages are not always removed automatically.

When using g:doomnvim_custom_plugins plugins can be installed but cannot be removed automatically.
The user must remove the corresponding lines in config/main and the directories in plugged/ to completely remove a plugin

==> May use vim-plug's snapshots to save state before new plugin

• Allow user to disable some plugins
• Allow user to add more plugins

The buffered terminal cannot be closed unless the exit command is used

Most user configuration must be done in the .doomrc file which is mostly blank by default. Making it readable and simplifying the use of this file will make it easier to customize doomnvim

• Use dashboard-nvim

Currently working on the dev branch

While doomnvim now creates the BFC file, it won't save the default parameters inside, like the colorscheme, rolling back to the default
doomnvim colorscheme

On default install of doomnvim, the .doomnvim file should be created and used to configure doomnvim.
At the moment this file is not created nor loaded