Fix encrypted properties tests to work with WSS4J 4.0.2

[coheigea]

The Jasypt algorithm changed, for now we'll just use the old encrypted values in the CXF tests until we pick up WSS4J 4.0.2 properly.

[reta]

@coheigea may I suggest please to have two independent test runs in Maven, non-FIPs as defaut:

<plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-surefire-plugin</artifactId>
                <executions>
                    <execution>
                        <id>default-test</id>
                        <configuration>
                            <systemPropertyVariables>
<org.apache.wss4j.crypto.jasypt.useLegacyDefaultAlgorithm>true</org.apache.wss4j.crypto.jasypt.useLegacyDefaultAlgorithm>
                            </systemPropertyVariables>
                        </configuration>
                    </execution>
</plugin>

And FIPS one:

<plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-surefire-plugin</artifactId>

                    <execution>
                        <id>fips-test</id>
                        <goals>
                            <goal>test</goal>
                        </goals>
                        <configuration>
                            <systemPropertyVariables>
                                <org.apache.wss4j.crypto.jasypt.useLegacyDefaultAlgorithm>false</org.apache.wss4j.crypto.jasypt.useLegacyDefaultAlgorithm>
                            </systemPropertyVariables>
                        </configuration>
                    </execution>
                </executions>
            </plugin>

More than happy to help with that, it is very difficult to eliminate side effects of system properties in tests, thank you.