only trigger deprecated warnings on using functionality which is actually deprecated

This contains changes required such that deprecation log messages are only hit when actual deprecated functionality is being relied upon.

This is necessary to make `--deprecated` useful, with the upcoming EasyBuild v2.0 release in mind. 

depends on https://github.com/hpcugent/vsc-base/pull/149


to avoid tripping a deprecation error with `--deprecated=2.0`...

just making the mapping is OK, using the old-style stuff is not, so we should only throw a deprecation warning/error when it's actually **used**