Updated: doc/bc/6.0/audit.md: the API, the index schema, the console, sinks, alerts, archives and the acceptance tests of the audit design

Updated: doc/bc/6.0/content-jobs.md describes states for a subtree, removing many locations, adding a location for many items and their tests

Added: Many locations can be removed, and a location added for many items, now or as a background job

Removing several locations in the locations window gives, for many of them or after the choice
"background", the confirmation with what it touches and a removelocation content job; a few are removed at
once as before. The sub items list's More actions offers "Add a location for selected": a browse page for the
new parent with what it touches and the choice, then the kernel's addlocation operation per object, or an
addlocation content job. Objects already placed there, and items that would go below themselves, are left
out. A subtree a background job is working on is refused in both.

Added: The node's states can be set for its whole subtree, now or as a background job

The states form of the Details tab offers "Also for everything below this node". Small subtrees, and the
choice "now", set the states on every object in the request through the kernel's updateobjectstate operation;
large ones get the confirmation with what it touches and the choice, and a state content job. The editor
must be allowed to assign the state to the node's own object; a subtree a job is working on is refused.
Without the option the form works as before.

Updated: The content job confirmation and summary handle selected locations

The confirmation sends a field with several values again (the selected locations, the selected states). The
summary of adding or removing locations counts the selected locations only, not what is below them, says
"Selected locations", shows for a removal the objects that keep other locations, and lists at most ten
items by name.

Updated: The run now or in the background choice of a browse page is sent with the browse form

A browse page renders its description, and with it the choice, above the browse form. The choice looked for
the form when it was rendered, found none and was never sent, so the move and copy browse pages applied the
automatic decision by SynchronousLimit whatever the editor chose. The choice now listens for the form's
submit on the document, whatever the order in the page.

Updated: doc/bc/6.0/audit.md: the event catalogue, the record format and the settings reference of the audit design