compile jsvc in own subshell with explicit LD_LIBRARY_PATH with /lib(32|64) appended

Apparently there is an issue with jsvc picking up the libcap.so
library.  Once upon a time it was in /usr/lib, now it is in
/lib(32|64), so adding to the LD_LIBRARY_PATH in hopes it gets picked
up and avoids tomcat jsvc build problem - as reportd by Luca:

- the most serious issue is that after upgrading Tomcat to 6.0.36,
  JSVC fails to start on my server because of missing
  /usr/lib.libcap.so. I had to manually symlink that library to get
  Tomcat started (see below)

o) issue: missing libcap.so prevents JSVC from starting:

failed loading capabilities library -- /usr/lib/libcap.so: cannot open shared object file: No such file or directory.
Cannot set group id for user 'tomcat'
set_user_group failed for user 'tomcat'
Service exit with a return value of 4

solution:
bash-3.2# ln -s /lib64/libcap.so /usr/lib/libcap.so

bash-3.2# ls -l /usr/lib/libcap.so
lrwxrwxrwx 1 root root 16 Apr 22 07:42 /usr/lib/libcap.so -> /lib64/libcap.so

----------
Instead of linking the library since it goes by the name of
libcap.so.2.  Currently if we can find the library, it should have the
same result.  (put it where it can be found vs let where it is be
known)
Move tomcat security related files to esg's config root

You should not have to get new certificates, etc. when updating or
installing a new tomcat.  These files should be considered part of the
node's "state" and thus held under /esg.

The server.xml file is adjusted accordingly to look at the
/esg/config/tomcat location for certificates and users.

Ex:

/esg/config/tomcat
drwxr-xr-x 3 tomcat tomcat   4096 Apr 22 19:33 Catalina
-rw-r--r-- 1 tomcat tomcat 181779 Apr 22 19:44 esg-truststore.ts
-rw-r--r-- 1 tomcat tomcat 182379 Apr 22 19:44 esg-truststore.ts.bak
-r-------- 1 tomcat tomcat    887 Apr 22 19:32 hostkey.pem
-rw-r--r-- 1 tomcat tomcat   1276 Apr 22 19:32 keystore-tomcat
-rw-r--r-- 1 tomcat tomcat    590 Apr 22 19:32 pcmdi11.llnl.gov-esg-node.csr
-rw-r--r-- 1 tomcat tomcat    733 Apr 22 19:32 pcmdi11.llnl.gov-esg-node.pem
-rw-r--r-- 1 tomcat tomcat    295 Apr 22 19:42 tomcat-users.xml
-rw------- 1 root   root      295 Apr 22 19:42 tomcat-users.xml.bak

/usr/local/tomcat/conf
drwxr-xr-x 3 tomcat tomcat  4096 Apr 22 19:42 Catalina
-rw------- 1 tomcat tomcat 10636 Oct 16  2012 catalina.policy
-rw------- 1 tomcat tomcat  3713 Oct 16  2012 catalina.properties
-rw------- 1 tomcat tomcat  1395 Oct 16  2012 context.xml
-rw------- 1 tomcat tomcat  3290 Oct 16  2012 logging.properties
-rw------- 1 tomcat tomcat  6865 Apr 22 19:42 server.xml
-rw------- 1 tomcat tomcat  6616 Apr 22 19:42 server.xml.bak
-rw------- 1 tomcat tomcat  1530 Oct 16  2012 tomcat-users.xml
-rw------- 1 tomcat tomcat 53131 Oct 16  2012 web.xml
Move certificates out of tomcat distribution's conf dir into esgf's config location

The idea here is to pull this bit of "state" out from under the tomcat
installation location and put it where esgf node state is kept
i.e. under ${ESGF_HOME}/config
More mature regex for server.xml 443 SSL connector stanza

Previously used @@foo@@ tokens to replace directly.
Now using a bit more sophisticated regex that is independed of tokens.

(will do that to other @@token@@ patterns used... later)
Put tomcat configuration migration code in single function

Move the files accordingly to new esgf location
Better checking of keystore credentials.

Make it so that when a new keystore is generated or any action that
triggers a call to "add_my_cert_to_truststore" that the passwords are
checked and adjusted accordingly.
uvcdat tagged at v1.3.0 - Also CDAT_HOME includes cdat version in path. Ex: /usr/local/uvcdat/1.3.0/....
Merge branch 'devel' into uvcdat-cmake-install