NEXUS-6882: Orient DB pool depletion

As learned from npm sources, it uses request package that in turn
uses Agent package that builds on node's http package. None of these
override http.maxSockets, hence npm client uses the default value
(if anyone knows differently, speak up!) which is 5.

This also explains why simple "load" tests worked with 2 npm
clients but depleted npm plugin OrientDB pool when 3+ npm was
running (default pool size was too low: 10).

This change also exposes the pool size settings via nexus.properties

Note: OrientDB default pool size is 100, unsure why such low size for
maxPool was chosen initially at all.

Issue
https://issues.sonatype.org/browse/NEXUS-6882

CI
http://bamboo.s/browse/NX-NPMF18
You're right. The initial goal of this PR was to increase pool size from a way too small 10 (enough for 2+ npm CLIs) to... erm, to something. And to expose the settings.

Am still looking for other means, like "guarding" the pool and preventing it being depleted for example (with thread requesting a connection remaining blocked with some timeout or so).