Fix for running unit tests that use the Chrono data directory.
Fix for running unit tests that use the Chrono data directory.

Because we use a relative path to the Chrono data directory, we must ensure that CTest executes the tests in the appropriate directory.  This requires specifying the WORKING_DIRECTORY test property.  However, matters are further complicated by the fact that VS places the executables in a subdirectory of ${EXECUTABLE_OUTPUT_PATH} (depending on the build configuration).

amelmquist/chrono,armanpazouki/chrono,jcmadsen/chrono,Milad-Rakhsha/chrono,jcmadsen/chrono,jcmadsen/chrono,projectchrono/chrono,rserban/chrono,dariomangoni/chrono,dariomangoni/chrono,rserban/chrono,Bryan-Peterson/chrono,amelmquist/chrono,armanpazouki/chrono,tjolsen/chrono,dariomangoni/chrono,jcmadsen/chrono,projectchrono/chrono,Milad-Rakhsha/chrono,jcmadsen/chrono,jcmadsen/chrono,projectchrono/chrono,tjolsen/chrono,armanpazouki/chrono,projectchrono/chrono,jcmadsen/chrono,tjolsen/chrono,dariomangoni/chrono,dariomangoni/chrono,andrewseidl/chrono,rserban/chrono,andrewseidl/chrono,dariomangoni/chrono,Milad-Rakhsha/chrono,Bryan-Peterson/chrono,tjolsen/chrono,projectchrono/chrono,Bryan-Peterson/chrono,andrewseidl/chrono,Milad-Rakhsha/chrono,Bryan-Peterson/chrono,rserban/chrono,armanpazouki/chrono,andrewseidl/chrono,Bryan-Peterson/chrono,amelmquist/chrono,amelmquist/chrono,projectchrono/chrono,Milad-Rakhsha/chrono,rserban/chrono,rserban/chrono,amelmquist/chrono,andrewseidl/chrono,rserban/chrono,amelmquist/chrono,tjolsen/chrono,armanpazouki/chrono,armanpazouki/chrono,Milad-Rakhsha/chrono