After the changes in PR #14428, the [`normalizeWhitespace` option](https://github.com/mozilla/pdf.js/blob/1087b4dffdf5884ad17669fda54c59dd810667d3/src/display/api.js#L1072-L1073) is now in most (or perhaps even all) cases being ignored and treated as if `normalizeWhitespace = true` is passed to the `PDFPageProxy.{getTextContent, streamTextContent}` methods.[1]

With the changes in PR #14428 we're now handling all whitespaces *consistently* in the `PartialEvaluator.getTextContent` method, which together with other (somewhat) recent improvements have fixed many textLayer issues by handling both coalescing of repeated spaces and proper space insertion between text chunks.
Looking briefly at this code, it seems to me that trying to re-instate "proper" `normalizeWhitespace = false` handling would be quite difficult and would likely hurt readability (assuming it's even at all possible now).
Furthermore, note that in both the viewer and the browser-tests we're only ever using `normalizeWhitespace = true` which means that the other code-path isn't really used all that much.

All-in-all, I'd probably suggest that we simply remove the `normalizeWhitespace` option and make the relevant methods always carry out the normalization since that's what e.g. the viewer uses.

Any thoughts/opinions about this?
/cc @timvandermeij 
/cc @calixteman 

---
[1] One example is the `issue6612.pdf` document in the test-suite, added together with the option, where "regular" spaces are now being returned regardless of the `normalizeWhitespace` value.
*   Any valid `canvas.fillStyle` can be used: a `DOMString` parsed as CSS
 *   <color> value, a `CanvasGradient` object (a linear or radial gradient) or
 *   a `CanvasPattern` object (a repetitive image). The default value is
 *   'rgb(255,255,255)'.
 * @property {Promise<OptionalContentConfig>} [optionalContentConfigPromise] -
 *   A promise that should resolve with an {@link OptionalContentConfig}
 *   created from `PDFDocumentProxy.getOptionalContentConfig`. If `null`,
 *   the configuration will be fetched automatically with the default visibility
 *   states set.
 * @property {Map<string, HTMLCanvasElement>} [annotationCanvasMap] - Map some
 *   annotation ids with canvases used to render them.
 */
/**
 * Page getOperatorList parameters.
 *
 * @typedef {Object} GetOperatorListParameters
 * @property {string} [intent] - Rendering intent, can be 'display', 'print',
 *   or 'any'. The default value is 'display'.
 * @property {number} [annotationMode] Controls which annotations are included
 *   in the operatorList, for annotations with appearance-data; the values from
 *   {@link AnnotationMode} should be used. The following values are supported:
 *    - `AnnotationMode.DISABLE`, which disables all annotations.
 *    - `AnnotationMode.ENABLE`, which includes all possible annotations (thus
 *      it also depends on the `intent`-option, see above).
 *    - `AnnotationMode.ENABLE_FORMS`, which excludes annotations that contain
 *      interactive form elements (those will be rendered in the display layer).
 *    - `AnnotationMode.ENABLE_STORAGE`, which includes all possible annotations
 *      (as above) but where interactive form elements are updated with data
 *      from the {@link AnnotationStorage}-instance; useful e.g. for printing.
 *   The default value is `AnnotationMode.ENABLE`.