Changing approach on build on tag and dev

Currently any push to dev forces rebuild of current dev branch and places newly built mpdroot inside the directory /cvmfs/nica.jinr.ru/centos7/mpdroot. This is quite dangerous as there may be several commits to dev in a short period making data in dev directory unreliable. We will not change the process as it is with SIMPATH build. In the non-SIMPATH build we will do the following changes:

1. on each push to dev we will build mpdroot as before and we will place it in the directory /cvmfs/nica.jinr.ru/sw/scratch/{os_version}/mpdroot/dev
2. if user creates tag - pointing to any point of git repository ending by word test (e.g. my_new_tag-test), the marked hash of repository will be built and the result will be placed to the directory /cvmfs/nica.jinr.ru/sw/scratch/{os_version}/mpdroot/my_new_tag
3. any other tag will force build of mpdroot in "Release" mode and such build will be placed to /cvmfs/nica.jinr.ru/sw/{os_version}/mpdroot/tag Note, that there is no guarantee on the integrity of data in scratch folder and therefore only tagged versions without the "-test" part should be used for production @mvala, @amoshkin