Add ability to disable auto-play for multi-frame subjects

[lcjohnso]

Problem: Some multi-frame subjects are not meant to be looped or viewed in sequence. Example: Nest Quest Go projects show the front and back of the nest observation card as two separate frames, where the auto-play option that blinks these two images is not desired. Instead, the app should be configurable so that it doesn't auto-play on mobile.

Solution: Either roll-back the default auto-play behavior (i.e., multiframe subject do not loop by default) and enable auto-play as a workflow or project level configuration option, OR allow workflow or project level configuration to override the auto-play default (i.e., configure workflows as "don't autoplay" for mobile purposes).

Considerations: We need to assess the relative numbers of cases for "auto-play is OK" vs. "auto-play is bad". We also need to consider how the current FEM multi-frame viewer's auto-play configuration option (see PR where option was added to lab: zooniverse/Panoptes-Front-End#6418) plays into this mobile-specific configuration option. Are they one in the same, or do we wish to be more aggressive about auto-play on mobile?

Exact steps to Reproduce
Steps to reproduce undesired autoplay behavior:

1. Open app, select any workflow from a Nest Quest Go Project (e.g., Eastern Bluebirds)
2. Upon loading the classifier, the image will blink between the front and back of the observation card. Blinking is unwanted behavior for a task that requires extracting text from certain fields on the card.