Undo cf863735 - Only create a project for...

...a directory if explicitly asked by user

• a little more to adjust newer stuff since cf863735

Hello Folks, I'm not happy because I fear nobody will agree or like it.

This branch was named with the intend to create some "Dummy Project" in case one opened a file which is not part of some project.

When you have some projects open, the plugin switch nicely with the current file. When you now open/switch to some file wich is not part of any project, the plugin did nothing. That is pretty bad. You got the impression the current file belongs to the project what the plugin shows. So far "fine" you will agree.

It pointed out, that a good (enough) solution is to just revert one patch. That's not perfect, because the git view give no hint that there is no git active, but that's much less an issue as the current situation and my got fixed.

Now the ugly part:

When starting Kate the current directory is implicitly "opened" as project which is a very bad situation. You ended easy up with a "Project" of you home folder. That's not nice.

I know that you guys like that feature "Open Folder" but that is a very bad choice in my opinion. And that this is the default behavior of Kate make it even worst. (At least is that my impression as described)

• First is the naming bad. With hat feature/action you open in fact nothing. Just the plugin is triggered to look at that path.
• Second, the solution as implemented.

If it could be fixed, that a folder is "opened" (in current terms) when a directory is explizit given on the command line, fine, keep that. If not we need an extra option for that feature. That would be in any case my choice in implementing such feature e.g. --project-path

Last note: What I would expect from an action "Open Folder" is, to open all files in that folder.