Enhance applySavedView API

[roluk]

Rework applySavedView settings interface to make it easier to understand.

Initially I designed it around the idea of extensions having three three operations: save, apply, and reset. While this system worked well for some applications, this confined the interface to a narrow applicability space and burdened users with a mental model that didn't necessarily match their expectations. This change is a step towards rethinking what it means to "apply a saved view", and making built-in EmphasizeElements and PerModelCategoryVisibility extensions first-class concepts of saved-views-react.

Breaking changes

• Make applySavedView settings easier to understand
  • Remove "reset" from ApplyStrategy union, instead make "clear" a valid value for emphasis and perModelCategoryVisibility properties
  • Remove all property which set default ApplyStrategy of all settings
  • Update documentation

Minor changes

• applySavedView enhancements
  • Accept custom viewChangeOptions that the function will internally pass through to viewport.changeView call
  • Add camera setting that controls how camera data is applied. Allow supplying a custom ViewPose or ignoring Saved View data to keep the camera in place.

Other

• Improve documentation
  • Add precision, change wording, and simplify examples
  • Remove mentions of savedviews:read and savedviews:modify because they have been superseded by itwin-platform scope
• Reformat code where it exceeds 100 columns in width, down from 120
  • Start breaking comments into new lines after reaching 80th column
• Simplify executeQuery use by making it return a flat list of ids

[diegopinate]

Looks good! I'd like to discuss your thoughts on how we should handle generic extensions later on.