scopelink: motor assignment, rotator, and the parameter tab as it now stands

[tothbastrolabs]

Follows indilib/indi-3rdparty PR #1386, which takes the driver to 1.1. The page needs to change with
it, and two things on it were already wrong.

• A "Which motor drives what" section. From interface 1.1 the controller holds which motor focuses,
  which rotates and which ones the front flap is made of. It decides which devices the driver offers,
  which calibrated travel belongs to which of them, and that the flap is opened by asking the controller
  for the flap rather than by moving a motor.
• A Rotator section, for the new INDI::RotatorInterface: what the calibrated travel means for the
  angles it will accept, that sync is an offset rather than a command sent to the controller, and what
  reverse does not do.
• The Parameters section describes the groups properly. A motor group is the motor — its currents,
  its acceleration — and belongs to it whatever it is driving; a job group is the job. That distinction
  is what 1.1 introduced.
• A correction: the page gave PARAM_FOCUSER_INVERT_DIRECTION in a copyable indi_setprop line. It
  has been PARAM_MOTOR1_INVERT_DIRECTION since the parameters were generated from the firmware's own
  description.
• A correction: an I²C had become a replacement character in two places.
• What a change to the assignment actually takes. The controller reads its configuration when it
  starts and drives from that copy, so a new assignment is stored and not acted on until it has been
  restarted — measured on hardware, where a rotator assigned while the controller ran was refused as
  having no motor assigned to it until it was restarted. The page says so, and says that Restart
  controller on the Parameters tab is what does it.
• Four troubleshooting entries: no focuser, rotator or dust cap where one was expected; an assignment
  the controller should never have accepted; a device that refuses everything because the controller
  has not restarted since it was assigned; and what a refused move means.
• categories and scopelink.yaml gain rotators; the version row reads 1.1.
• Screenshots. All fourteen were taken in one sitting on a generation 3 controller reflashed to
  interface 1.1, so the set is consistent with itself and with the driver as it stands. rotator.webp
  and firmware.webp are new — the Firmware tab had never had an image — and options.webp had to be
  re-taken regardless of this work, because it still offered a hardware generation the driver dropped.
  The Parameters tab now takes two: the restart action sits ten rows below the assignment and no single
  frame holds both, so parameters.webp shows the bottom of the pane, where the file actions and the
  restart are, and assignment.webp shows the assignment itself in the section that explains it.
  The rotator was photographed with the flap's motor lent to it, which is the only way a two motor
  controller can show a rotator at all.