Database & Testing update

### In this PR are some structural changes to tests:
 - No database URLs or credentials are stored in the project (source code, config or otherwise)
 - All Database info & creds are retrieved via `CrsProperties`
 - All tests which interact with the database extend `AbstractTestWithDatabaseConnectivity`
 - `AbstractTestWithDatabaseConnectivity` does a refresh of the target database before each test run

### Necessary changes:
 - Add profiles which contain DB URL, user & password to maven settings.xml (usually found at ~/.m2/settings.xml).  See below for example.

### Known side effects:
 - Tests can no longer be run inside intelliJ as even when running a maven goal inside the IDE, the properties don't get set in src/test/resources/default-properties.xml
 - When running tests from CL, a profile must be specified.  See example:

### Possible gotchas:
 - Do not EVER put production creds as a profile like this, as a test run could wipe out the production database.  There is no reason to do so.  Production creds should reside only in the application properties.  Actually you could try, but I'll likely make it that the prod DB would ignore connections things other than app servers.

Example profile:
```xml
<profiles>
        <profile>
                <id>eventhub-local</id>
                <properties>
                        <database.url>jdbc:postgresql://localhost/crsdb</database.url>
                        <database.username>crsuser</database.username>
                        <database.password>[password]</database.password>
                </properties>
        </profile>

        <profile>
                <id>eventhub-unittest</id>
                <properties>
                        <database.url>jdbc:postgresql://[remote-ip/host]/crs_unittest</database.url>
                        <database.username>crs_unittest_user</database.username>
                        <database.password>[password]</database.password>
                </properties>
        </profile>
</profiles>
```
Example test run:
```
bash: mvn clean test -Dgroups=[functional-tests,dbtest,unittest] -P [eventhub-unittest]
```
Since we are no longer specifying by way of the pom maven-surefire-plugin which groups it should include in the test phase, I think you can delete the entire plugin therein as it seems to be provided by default as part of maven core plugins.