VASP parser INCAR
The new parser catches quite some INCAR parameters more, which causes a lot of warnings. At the moment, this is a problem, due to the high amounts of warnings that will spam our logging system.
Due to the amount of possible INCAR parameters, the fact that they are all defined in two flavours ("in" user set, "inOut" set by VASP), and that they are often not well documented by VASP itself, I don't think they should be covered by individual metainfo definitions.
There are two solutions. Either, keep track of the missing definitions during parsing and then log once at the end with a list of keys. Or, we finally add dict support to the metainfo and store all INCAR parameters in one or two (in, inOut) dictionaries without specific definitions for each INCAR parameter.