Look more places for an executable

[GiudGiud]

Sweep as many places as possible, most of the syntax auto-complete can be done with any executable found. And tell the user which one VSCode found.

Look in order at

• local folder
• ~/projects/<any_folder>/ *opt/devel/etc
• ~projects/moose/test. and modules/<any_folder>
• conda moose environment executable

Skip the broken ones (ones that cant produce file dumps)

[DanShort12]

Came across a use for this earlier today too. We have a project with HIT files stored separately from the corresponding executable, so it would be good to be able to point to a language server outside of the current project. Perhaps introducing a configuration property along the lines of languageServerMoose.path that could point to a specific executable (or directory to search, with a default of current project to get approximately the current behaviour?) would be a fairly generic solution? It could also help for #13 e.g., if set to null then don't look for a language server.

[dschwen]

Dan that's a good idea and would work well with workspace specific configurations. I'll implement that.