- if enableDBSSL is false than clear keystore/truststore system properties

Needed to perform continous testing because there are tests set run with enableDBSSL=true and enableDBSSL=false.
The second continouse run break the tests with enableDBSSL=false like GoogleControllerSpec because the system properties
for keystore and truststore are setted by the first run of tests with enableDBSSL=true.
- added public/products-e2e.html to the bower post install step

The file products-e2e.html is used for the e2e testing with karma and should be similar to the products.html file with all
javascript dependencies. So the file producst-e2e.html is now also be managed with bower like the products.html file.
- removed cryptojslib bower dependency

The cryptojslib project bower configuration was not configured like expected so don't use it anymore
and rollback to the old state where the needed cryptojs files are imported in the main html file.
- added new method encryptString to reduce ugly code

Before the change you had to enrypt a string like that "Total".encrypt.encrypted now its simplere and can
be done like that "Total".encryptString.
- optimize defined npm test script

Removed the hard sleep statement of 30 seconds and configure wget call that determinate when the test server
instance is ready to try it 40 times and wait between this tries 10 seconds so that it wait for the server to be
ready 400 seconds in total. For a better continous local run of npm test first remove the RUNNING_PID file so that
play start will start a new server.

At the moment an play stop is missing for local run so if you made changes on the scala files you have to kill the
play server manualy and than you can perform npm test. A better solution will come in the future i hope but at the moment
it run very well on travis ci.
- implements new e2e test scenarion with a new user that has encrypted values store in the database

For the new test scenarion it was nessary to implements a possibility for the e2e tests
to specify which user the need for its tests. There are 2 users first user (email=testemail) with unencrypted values for balances and stocks
and second user (email=testemailenc) witn encrypted values for balances the default encryption key was used.

Backend changes: - added the new user (email=testemailenc)
		 - add play integration test that check if the new user exists

Frontend changes: - added new route in the app.js (/testlogin/:googleid) to login with different test users
		  - replaced hard coded testuser in oauthcontroller-mock.js with the :googleid route parameter

Added the new test scenario to the scenarios.js file.
- merged online github changes with local working copy changes both changes are from me	public/js/bankapp/app.js