Back-end can now choose how to be loaded up - either using MySQL (production) or in-memory H2 (for development).

Choosing the profile which to use is very simple:

 -Dspring.profiles.active="dev" if you would like to load up the back-end using in-memory H2,
 -Dspring.profiles.active="production" if you would like to load up the back-end using MySQL.
Tests were fixed following Apache Shiro's introduction. APISecurityUtil (A util which was written to avoid shiro boilerplate) has been converted from static to a normal POJO which is then wired as a Spring bean.

Controllers can therefore make use of such a bean with @Autowired. This was necessary in order to be able to mock the util.
Update to "dev" profile (embedded H2 database).

- Along with the auto-creation of tables, import.sql now creates three coins and a BACKOFFICE user (admin/Password123) for starters.
- Added the web view of the H2 database - great for debugging purposes. Visit http://127.0.0.1:8082
flipeuro-product-singleapp has been replaced by flipeuro-singlepage-app.

flipeuro-singlepage-app is an independent war file which can be deployed on its own, expecting to find the back-end REST API services on the same domain - it is therefore ideal host the API on the same container.

flipeuro-singlepage-app has most of the processes implemented. More to follow:
- API must be polished and more consistent per call. Sign-up must return the user details as part of the response, Deposit must return the new balance as part of the response, Error code must not be returned in Http200, and so on...
- play screen must be implemented
- sign-up screen must be implemented
- sign-out screen must rest all context (isloggedin, balance, coins, etc)