CAS configuration once loaded overrides the other application configuration

The code in SpringSecurityCasGrailsPlugin - loads "**DefaultCasSecurityConfig**"
```
`SpringSecurityUtils.loadSecondaryConfig 'DefaultCasSecurityConfig'
// have to get again after overlaying DefaultCasSecurityConfig
conf = SpringSecurityUtils.securityConfig

if (!conf.cas.active) {
return
}`
```
And in "**DefaultCasSecurityConfig**" there are default CAS configuration which are now loaded whenever the Plugin is included irrespective the active flag is true of false.

In similar line there is SAML plugin **SpringSecuritySamlGrailsPlugin**. The above mentioned code is commented.

Code in the CAS plugin need to be commented too. This will ensure that default CAS configuration wouldn't be loaded by default whenever this plugin is included.

Start in SpringSecurityCasGrailsPlugin and compare its configuration handling with SpringSecuritySamlGrailsPlugin. Trace when DefaultCasSecurityConfig is loaded relative to the CAS active flag; done means inactive CAS configuration is not loaded merely because the plugin is included.

Written by the indexing model from the issue text.