Bug #4043 create_glidein fails with error on missing clientlogs/glideinlogs/clientproxies directories

The creation of the necessary client directories, when privilege separation is
in effect, requires the use of HTCondor's condor_root_switchboard.  It appears
that between v7.9.1 and v7.9.4 it's behavior changed.  The switchboard is
not really documented explicitely so troubleshooting was performed pretty
much by trial and error and observation.
.
In v7.9.1, the 1st level client log/proxies directory (user_USERNAME) is
created using a 'mkdir' argument and had 755 permissions set by default.
The lower level directories use an 'exec' argument executing '/bin/mkdir' with
permissions getting set to 0755 by default.  On the lowest level client proxies
directories, a directory for each factory entry point is created with
permissions explicitely set to 0700 by running the switchboard with the 'exec'
arg executing '/bin/mkdir -m 0700'.
.
drwxr-xr-x 3 root   root   4096 Jun 13 08:50 logs
drwxr-xr-x 3 cms_vo cms_vo 4096 Jun 13 08:50 logs/user_cms_vo
drwxr-xr-x 3 cms_vo cms_vo 4096 Jun 13 08:50 logs/user_cms_vo/glidein_master
drwxr-xr-x 2 cms_vo cms_vo 4096 Jun 13 08:50 logs/user_cms_vo/glidein_master/entry_ress_ITB_INSTALL_TEST_2
.
drwxr-xr-x 3 root   root   4096 Jun 13 08:50 proxies
drwxr-xr-x 3 cms_vo cms_vo 4096 Jun 13 08:50 proxies/user_cms_vo
drwxr-xr-x 3 cms_vo cms_vo 4096 Jun 13 08:50 proxies/user_cms_vo/glidein_master
drwx------ 2 cms_vo cms_vo 4096 Jun 13 08:50 proxies/user_cms_vo/glidein_master/entry_ress_ITB_INSTALL_TEST_2
.
In v7.9.4 (or after 7.9.1), this changed.  The 1st level client log/proxies
(user_USERNAME) directories were getting set to 0700.
Since condor_root_switchboard does not always give good return codes or
requires looking in stderr for a message, the create_glideins does it own
verification that the directories were created and if they were not, rolls back
the directory structure by running the switchboard with an 'rmdir' argument.
So, unless you force a sleep, nothing will appear to have been created.
At the bottom level of the proxies directory structure the 'mkdir -m 0700' also
did not appear to be functional anymore and the entry level proxy directories were
being set to 0755.
.
drwx------ 3 root   root   4096 Jun 13 08:50 logs
drwxr-xr-x 3 cms_vo cms_vo 4096 Jun 13 08:50 logs/user_cms_vo
drwxr-xr-x 3 cms_vo cms_vo 4096 Jun 13 08:50 logs/user_cms_vo/glidein_master
drwxr-xr-x 2 cms_vo cms_vo 4096 Jun 13 08:50 logs/user_cms_vo/glidein_master/entry_ress_ITB_INSTALL_TEST_2
.
drwx------ 3 root   root   4096 Jun 13 08:50 proxies
drwxr-xr-x 3 cms_vo cms_vo 4096 Jun 13 08:50 proxies/user_cms_vo
drwxr-xr-x 3 cms_vo cms_vo 4096 Jun 13 08:50 proxies/user_cms_vo/glidein_master
drwxr-xr-x 2 cms_vo cms_vo 4096 Jun 13 08:50 proxies/user_cms_vo/glidein_master/entry_ress_ITB_INSTALL_TEST_2
.
Rather than depend on default behavior in condor_root_switchboard, the changes
made perform the same series of mkdir's but I added an explicit execution of
the switchboard doing the appropriate chmod for permissions.
.
Of note, this may be of interest regarding the future of PrivilegeSeparation and
may have been a factor in the changed behavior:
  https://www-auth.cs.wisc.edu/lists/htcondor-devel/2013-April/msg00008.shtml