FixtureService.removeFixture now returns a partial model

It's more convenient to get the fixture ID from the response body, so we
now return a fixture model with nothing but the ID in it.
return the partial fixture model in the response body when removing
initial implementation of removeFixtureFromView

This implementation simply locates the row and removes it.  Still need
to do something to draw user's attention to the row just before it is
removed.
implemented the remove fixture strategy
replace ID placeholder in row controls
made a shared logger for functional tests
when removing last fixture from table must look for "empty" row

When jquery.dataTables removes the last row from the table, it inserts a
row with a single cell with a class to identify that it's empty.
fixed a broken functional test

Must specify a version when inserting data for hibernate to modify or
delete when optimistic locking is in use.  If the version column is
null, SQL ternary logic causes hibernate to incorrectly detect an
optimistic lock violation when attempting to update or delete the row.
configured POM to allow integration tests to be run from eclipse

Essentially, this involves moving all of the automated integration setup
that would happen during a build to a profile that is active by default.
This profile is the "automated-integration-tests" profile in the POM.
Additionally, an "ide-integration-tests" profile is added to the POM.
It sets values for all of the properties used for integration testing.
These properties get filtered into test resources in the usual way.  As
long as the "ide-integration-tests" profile is enabled, the
"automated-integration-tests" profile will disable itself.

See the UAlerts wiki for instructions on running integration tests
within Eclipse.
added the "ide-integration-tests" profile to project configuration so
that integration tests can be run from within the IDE.