Add public API methods for accessing counts of Major Compaciton, Minor Compactions, and Active/Queued counts

[SethSmucker]

Is your feature request related to a problem? Please describe.
The ability to access counts of Major Compactions, Minor Compactions, and Active/Queued counts is gated behind the use of non-public classes. We need to be able to access this information in Datawave via the public API.

Describe the solution you'd like
InstanceOperations currently has a method called "getActiveCompactions()", but lacks methods for the other counts listed above (Maj/Min, Active/Queued)

Describe alternatives you've considered
We're currently using ManagerClientService, ClientContext, and ThriftClientTypes to get the number of compactions, but these are not part of the public API.

Additional context
Related Datawave PR

[ddanielr]

@DomGarguilo Additions to the public API are most likely out of scope for a bugfix release (2.1.5).

Adding this information at this point has the ability to constrict internal class modifications. We have exposed some of this info via metrics but not at per-table level due to cardinality issues.

We should probably discuss how to best expose this info while keeping it separate from the public API to allow for internal code changes.

I could see this taking the form of some sort of table info query API vs an administration API.

[DomGarguilo]

@DomGarguilo Additions to the public API are most likely out of scope for a bugfix release (2.1.5).

Yea I figured as much I just know thats the version that the mentioned project uses at the moment.

I could see this taking the form of some sort of table info query API vs an administration API.

Thats an interesting idea. Maybe something like a read-only API. Seems like this could often be useful for any systems that use accumulo. Being able to get this sort of info without having to pull from the metrics seems useful.

[dlmarion]

I could see this taking the form of some sort of table info query API vs an administration API.

This might be do-able in 4.0, but I'm not sure how you would do this in 2.1. The metrics are emitted from the TabletServer and Compactors. I don't think this information is aggregated anywhere in the code besides the ManagerMonitorInfo.