Document new Query service settings

New Query settings:

Setting                  CLI parameter              Default             Units/Type

node-quota               queryNodeQuota             0 (no quota)        MiB/integer

  This is the soft memory limit for the node.  It is the target the garbage collector will try to keep below.  

  NOTE: It is not a hard/absolute limit and memory usage may exceed this value.

node-quota-val-percent   queryNodeQuotaValPercent   67                  percent

  Percent of node-quota dedicated to tracked value content memory across all active requests.  Range (0-100).  (See: queryMemoryQuota for per-request equivalent.)

num-cpus                 queryNumCpus               0 (all available)   integer

  The number of CPUs the Query service can use.  The upper limit is the number available (or Community Edition limits).

  NOTE: This setting is requires a (re)start of the Query service to take effect.

completed-max-plan-size  queryCompletedMaxPlanSize  262144              bytes/integer

  Limits the size of query execution plans captured in completed_requests.  Range (0-20840448); values larger than the upper limit are silently treated as the upper limit.  Queries with plans larger than this do not have their plans captured and execution plans for such queries must be obtained via profiling and/or explain.