ControlService "type" rules/conventions

ControlService is documented as being usable by applications (as well as Quarks).

Its documentation needs to be improved so applications know the rules/conventions for choosing "type" values they register their mbeans with so as to avoid collisions - e.g., with the values that the runtime is using. Right now the runtime isn't doing anything to qualify the type names it's using (e.g., "job").

Rules/conventions for "identifier" values are also needed for avoiding collisions. e.g., runtime uses JOB_<n> Also need to clarify if it's legal for multiple registrations (different beans) for the same "id" and/or alias.