Changes to xml files associated with orp authentication to make xsd versions congruous with new Spring jar updates

Nicolas' tests yeilded the following recommendations:

-----email-----
Hi Gavin,

OK, I could solve these problems on my test data/compute node. All of this should be good soon!

I started this morning from a fresh clean server and installed what is in devel.

1/ - I did not get the errors you posted below because I do not have a
test IDP/Index node yet. I just have the production one for now. I am
working on it... But, I would say that the first exception below is
due to a spring-asm dependency. Could you try to remove every
spring-asm jar from your webapps and try again? On my side, I will set
up a test env soon...

2/ - As you upgraded spring-security to 3.1.4 all over the board, here
is what should be done on esg-orp configuration files:

/usr/local/tomcat/webapps/esg-orp/WEB-INF/classes/esg/orp/orp/config/security-context-auth.xml
-> Replace each occurence of 3.2.xsd with 3.1.xsd, despite what I said
last time...
/usr/local/tomcat/webapps/esg-orp/WEB-INF/classes/esg/orp/orp/config/web-context.xml
-> Replace each occurence of 3.2.xsd with 3.0.xsd, despite what I said
last time...
/usr/local/tomcat/webapps/esg-orp/WEB-INF/classes/esg/orp/orp/config/security-context-authz.xml
-> Replace each occurence of 3.0.xsd with 3.1.xsd, this one is a NEW
modif !!!
---------------

These summarize the changes in this commit.