Issue 35209

In valgrind versions newer than 2.0.0 (e.g. the latest stable 2.2.0 release),
soffice crashes during startup due to resource files (*.res) not found. This
needs to be fixed in order to ensure further OOo testability using valgrind,
callgrind et al.

Resource files (*.res) are located under '.../program/resource/' and are
searched for using 'osl_getExecutableFile()', which is supposed to return
'.../program/soffice.bin'. When run under valgrind, it happens to return
'/usr/local/bin/valgrind' instead, and resource files are thus searched for (and
obviously not found) under '/usr/local/bin/...'.

The function 'osl_getExecutableFile()', and the related functions
'osl_getCommandArg[Count]()', are based on unportable assumptions about how to
obtain a processes command line (e.g. via the '/proc' filesystem), instead of
relying on a standardized API 'main(int argc, char * argv[])', and those
assumptions do fail here (and can do so elsewhere).

A proposed fix introduces a new function 'osl_setCommandArgs(int argc, char *
argv[])', and adapts the various main() functions accordingly (ideally they
already use the recommended 'SAL_IMPLEMENT_MAIN()' macro).