Support requesting thumbnail-size images from the Imagery view

[akhenry]

Is your feature request related to a problem? Please describe.
In Open MCT images are currently defined by a URL, which either links to a file on a server, or includes a base-64 encoded image. There is a need to support requesting images at various scales (if the backend supports it). The imagery view should provide sufficient information to providers to allow them to make an intelligent decision about which scale to use when retrieving an image. Initially, let's focus on thumbnail images.

Thumbnail image are presented in the "filmstrip" view of image history shown at the bottom of the image view as in the example below.

Describe the solution you'd like
One way of handling this is to pass an option with the request for historical imagery that designates that this is a "thumbnails" request. This would work like the "strategy" option we use for "latest" and "min-max" type requests in other places. eg.

const thumbnails = await openmct.telemetry.request(imageDomainObject, {scale: "thumbnail"});

Additional context
This will complement VIPEROMCT-208 which is exploring the use of an apache module for doing dynamic image resizing.

[ozyx]

Testing Instructions

1. Create a new "Example Imagery" object
2. Inspect one of the image thumbnails
3. Verify that the thumbnail img src has url params "?w=100&h=100"
4. Inspect the main image
5. Verify that it does not contain the same url params
6. Create a Time Strip
7. Drag the Example Imagery into the time strip
8. Hover over the timestrip or adjust bounds to show just a few images and inspect one of the image thumbnails
9. Verify it has the same thumbnail url params
10. Click on the image to "View Large"
11. Inspect the main image, verify it does not have the thumbnail params
12. Inspect the thumbnails, verify they do have the thumbnail params

[khalidadil]

Verified Fixed in Testathon on 01/24/23

[unlikelyzero]

Need two more folks to test this after YAMCS upgrade

[khalidadil]

Verified this again after yamcs upgrade - Testathon 02/06/23

[michaelrogers]

Fix verified during testathon 02/06/2023 for example imagery.