Add request origination self identifier for Java API metrics

[popzip]

Using Telemetry, we can track feature usage at a granular level. For example, the Optic API will be tracking # of joins. We need a way to track where a request originated when coming from the Client APIs. Each client API must include some sort of identifier that the server can use to increment the correct metric (e.g. optic-joins-javascript vs optic-joins-java).

This task is not for a specific metric - just adding the JAVA identifier that can be used by feature tracking mechanism.

[sammefford]

I verified this is working by running the RowManagerTest, then looking in the meters database at all ".../features.xml" files, and seeing that some of them had features that had "java" in the name. For example, I saw this:

<feature-metrics xmlns="http://marklogic.com/xdmp/usage-meters">
  <start-time>2017-02-02T14:00:00.861079-08:00</start-time>
  <end-time>2017-02-02T15:00:00.37058-08:00</end-time>
  <cluster-id>18318090550103575909</cluster-id>
  <host-id>1152935850970130845</host-id>
  <group-id>12708412972638519771</group-id>
  <cluster-name>smefford-z620.marklogic.com-cluster</cluster-name>
  <host-name>smefford-z620.marklogic.com</host-name>
  <group-name>Default</group-name>
  <features>
    <feature name="op.doc.qry.rest.sjs">2</feature>
    <feature name="op.rows.groupbys.rest.sjs">1</feature>
    <feature name="op.views.java.sjs">6</feature>
    <feature name="op.views.rest.sjs">3</feature>
    <feature name="xdmp.sql.queryCount">7</feature>
    <feature name="op.triples.rest.sjs">1</feature>
    <feature name="op.lexicons.java.sjs">2</feature>
    <feature name="op.rows.groupbys.java.sjs">2</feature>
    <feature name="cts.plugin.icu.ta.lexerCount">2</feature>
    <feature name="op.doc.qry.java.sjs">4</feature>
    <feature name="op.results.java.sjs">377</feature>
    <feature name="temporal.doc">12</feature>
    <feature name="temporal.protect">6</feature>
    <feature name="cts.plugin.bitext.en.stemmerCount">76</feature>
    <feature name="op.results.rest.sjs">26</feature>
    <feature name="op.lexicons.rest.sjs">1</feature>
    <feature name="op.triples.java.sjs">2</feature>
    <feature name="sem.sparql.queryCount">31</feature>
    <feature name="temporal.version">44</feature>
  </features>
</feature-metrics>

@popzip @ehennum do those feature identifiers look like what we expect?