libs: update nfs code to 0.7.2

The libdcap can distinct between regular file systems
and dCache's NFS. This is achieved by existence of a
magic file '.(get)(cursor)', which can be accessed in
any directory in dCache's namespace. Nevertheless, this
behaviour prevents dcap-aware clients to access dcache
through NFSv4.1.

The updated version of nfs library adds a possibility to
hide magic file from dcap client and force them to treat
dCache's NFS as a regular file system.

New export options added: dcap(defualt) and no_dcap.

Example:

/pnfs 10.0.1.1/24(rw,acl,no_dcap)

Changelog for nfs4j-0.7.1..nfs4j-0.7.2
    * [5c4808c] vfs: add a special option to hide dcache from dcap clients

Acked-by: Gerd Behrmann
Target: master, 2.7, 2.8
Require-book: yes
Require-notes: yes
Add alarms and transfermanager database to system-test setup

HSQLDB conection parameters are defined too, although the alarms schema
is limited to postgresql at the moment. For that reason and because
HSQLDB is a single process database, the alarms service uses the xml
store.

The httpd.alarms.* properties are marked immutable, as modifying many of
them will have no effect as they are not used as part of the definitions
of derived properties (e.g. changing httpd.alarms.db.type had no effect).

Target: trunk
Require-notes: no
Require-book: no
Acked-by: Albert Rossi <arossi@fnal.gov>
Patch: http://rb.dcache.org/r/6534/
Drop JDBC driver properties

JDBC 4 drivers auto-register through the Java ServiceLoader facility. It
is no longer recommended to load the driver through Class.forName. This
allows us to get rid of all the db.driver properties (which where not DRY
anyway, as the driver identification was duplicated between the driver
property and the url property).

DataNucleus unfortunately insists on loading something, so for the time
being I gave it a dummy class to load (java.lang.String). An upcomming
patch will solve this while moving everything to HikariCP.

The patch marks all *.db.driver properties as obsolete. Use of JDBC 4
compliant drivers is required.

Target: trunk
Require-notes: yes
Require-book: yes
Acked-by: Albert Rossi <arossi@fnal.gov>
Acked-by: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
Patch: http://rb.dcache.org/r/6535/
Use Spring's Environment and PropertySource feature to inject configuration

Spring 3.1 introduced the Spring Environment, which provides a flexible way
to add additional property sources. This patch updates UniversalSpringCell
to inject our configuration into the context as property sources. This allows
us to get rid of dCache specific boilerplate in our Spring XML files.

Target: trunk
Require-notes: no
Require-book: no
Acked-by: Albert Rossi <arossi@fnal.gov>
Patch: http://rb.dcache.org/r/6536/
webadmin: Inject service configuration into Spring environment

This allows the properties to be used more widely, such as for activating
profiles.

Target: trunk
Require-notes: no
Require-book: no
Acked-by: Albert Rossi <arossi@fnal.gov>
Patch: http://rb.dcache.org/r/6537/
dcache-core, alarms: remove postgresql precondition on schema

There is nothing in the liquibase schema for alarms which specifically requires postgresql.
Removing this precondition allows the rdbms option to be tested in system-test using hsqldb.

Target: master
Request: 2.8
Request: 2.7
Request: 2.6
Patch: http://rb.dcache.org/r/6548/
Require-book: no
Require-notes: no
Acked-by: Gerd
Use HikariCP connection pool in most services

After having tested HikariCP as part of space manager, the next step is to try
it for other services. In the interest of maximizing internal testing before
public release, this patch switches most services to HikariCP. A few services
require a bit more work and will be updated in a separate patch.

Since DataNucleus doesn't have direct support for HikariCP, the patch changes
DataNucleus invocation to inject a pre-configured data source.

A custom DriverManagerDataSource had to be added to chimera as HikariCP only
works with DataSources, not DriverManager directly.

Most *.db.connections.partition-count properties are gone, and
*.db.connections.{min,max}-per-partition have been replaced by
*.db.connections.{min,max}.

Target: trunk
Require-notes: yes
Require-book: yes
Acked-by: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
Patch: http://rb.dcache.org/r/6538/
billing,webadmin,alarms: Use HikariCP

I had to refactor the code somewhat to make it easy to inject other data
sources that what DataNucleus can create itself. As far as possible I have
moved instantiation and wiring into Spring, thus removing lots of glue code.

With this patch, all *.db.connections.partition-count properties are obsolete
and *.db.connection.{min,max}-per-partition have all been renamed to
*.db.connection.{min,max}.

Target: trunk
Require-notes: yes
Require-book: yes
Acked-by: Albert Rossi <arossi@fnal.gov>
Patch: http://rb.dcache.org/r/6541/
libs: update to bugfix nfs4j-0.7.3

Changelog for nfs4j-0.7.2..nfs4j-0.7.3
    * [f2b0d2b] vfs: fix regression introduced in 1c916c5

Acked-by: Gerd Behrmann
Target: master, 2.8, 2.7
Require-book: no
Require-notes: no
core, billing: remove unit test

The unit test for billing persistence uses timeouts/sleep to check the presence and absence of entries in the database.  This timing, however, is inherently unstable because it depends on the OS and the thread scheduler in particular.  Thus the test will sometimes fail during the build process.

However, the usefulness of this test is very limited, so I propose simply to eliminate it.

Target: master
Request: 2.8
Request: 2.7
Request: 2.6
Request: 2.2
Patch: http://rb.dcache.org/r/6556/
Require-book: no
Require-notes: no
Acked-by: Gerd
Acked-by: Pau