Umd 3 htcondor

Here is first version of the templates for configuring Cream-ce with htcondor batch system. A number of features is still missing (e.g. possibility to run cream and htcondor master on 2 different machines).

the comment is indeed a bit laconic. The point here is that condor_local_submit_attributes.sh is called inside condor_submit.sh (which is part of glite-ce-blahp) to customize the submission file. Now, the x509userproxy variable is defined inside condor_submit but not exported so it does not propagate to condor_local_submit_attributes.sh which forces me to recover the location of the proxy from SUDO_COMMAND variable. This is what is ugly: having to parse a variable value to get an information which is already in the env of the parent script. But, well, there is not alternative unless condor_submit.sh is not changed. I'll probably put a more clear comment to this line.