Common linters by default in the Build menu

This is a start of the effort to provide a bit more integrated development solution. Eclipse, Vim, Sublime, etc. modern IDE/editors allow for common linters to highlight erroneous and _smelly_ source code lines, some even on-the-fly in the marker margin.

Providing the configured default linter options in `data/filetype.*` files is a cheap and easy hack achieving somewhat similar functionality. The user still needs to have installed the linters they want to use. As discussed with @b4n on IRC, this is in order.

I did my best to research the most common linter packages for a particular language, opting for nothing in particular where there are variety of options with lack of consensus.

Additionally, I migrated old-style `[build_settings]` config blocks to new-style `[build-menu]` in a separate commit. Supposedly, @elextr or someone besides @b4n has to confirm that `build-menu.FT_00_CM` won't override user's custom set `build_settings.compiler` or similar. Be that the case, I can happily migrate `compiler`/`linker`/`run_cmd` commands in other filedef files as well.
I have no idea, but aren't those compile and lint commands redundant?  And can Ruby really be compiled or was it just a convenient action, like `php -l` for PHP?
I have no problem with having both if e.g. `-c` will only check if it's valid code and `-wc` would also check for various suboptimal/potentially problematic things, I'm merely checking for redundancy