LG-4381: Log Acuant SDK load on frontend

[aduth]

Why: To better understand issues that users may be having in completing the document capture step of the IAL2 flow, we should have insight into potential Acuant SDK load failures.

The details of the errors weren't known prior to starting the task. Documented here, they appear to be largely misconfiguration issues, ones which we likely won't often encounter. More interesting may be the sorts of errors that could be expected after Acuant SDK loads, and when the user attempts to start capture. This could be part of the discovery work involved in LG-4390.

[aduth]

These changes only move up the analytics provider. It's easier to see using "Hide whitespace changes" setting in GitHub:

[aduth]

Related: Following a prior similar comment about moving to some flattened, "composed" provider implementation, I explored this a bit. I think it may help improve diffs in review, though I think the general readability does suffer a bit, at least in the explored implementation.

function ComposeComponents({ components, children }) {
  return components.reduceRight(
    (result, [Provider, props]) => (
      // eslint-disable-next-line react/jsx-props-no-spreading
      <Provider {...props}>{result}</Provider>
    ),
    children
  );
}

render(
  <ComposeComponents
    components={[
      [DeviceContext.Provider, { value: device }],
      [AnalyticsContext.Provider, { value: { addPageAction, noticeError } }],
      [
        AcuantContextProvider,
        {
          credentials: getMetaContent("acuant-sdk-initialization-creds"),
          endpoint: getMetaContent("acuant-sdk-initialization-endpoint"),
        },
      ],
      [
        UploadContextProvider,
        {
          endpoint: /** @type {string} */ (appRoot.getAttribute(
            "data-endpoint"
          )),
          statusEndpoint: /** @type {string} */ (appRoot.getAttribute(
            "data-status-endpoint"
          )),
          statusPollInterval:
            Number(appRoot.getAttribute("data-status-poll-interval-ms")) ||
            undefined,
          method: isAsyncForm ? "PUT" : "POST",
          csrf,
          isMockClient,
          backgroundUploadURLs,
          backgroundUploadEncryptKey,
          formData,
        },
      ],
      [I18nContext.Provider, { value: i18n.strings }],
      [ServiceProviderContext.Provider, { value: getServiceProvider() }],
      [AssetContext.Provider, { value: assets }],
    ]}
  >
    <DocumentCapture isAsyncForm={isAsyncForm} onStepChange={keepAlive} />
  </ComposeComponents>,
  appRoot
);

[zachmargolis]

I agree -- a little diff noise here and there seems easier than trying to mentally unpack the loop

[mitchellhenke]

👍🏼 👍🏼 👍🏼

[zachmargolis]

LGTM