ocrImageType is not configurable via headers in tika-server

If a user sets the OCRImageType as a string, we aren't adding it to the "userConfigured" set which is used to decide what to modify during a clone operation of the PDFParserConfig.

This happens when users try to specify an ocr image type via headers in tika-server. The fix is trivial.