Removed ProcessPeakJob execution

[kjallen]

This is part 1 of resolving the ProcessPeakJob wav form generation. This PR completely removes the call of ProcessPeakJob calls, but does not remove the function definition.

If wav form image data already exists, it will not be removed when re-importing a record. If the record is new, a wav form image will not be created. Existing wav form image data is in JSON format and stored in Solr.

To confirm:

• Clone repo
• Rebuild using docker compose up --build
• Navigate to http://127.0.0.1:8000/admin
• Use [email protected] and password as credentials
• Click Destroy All Delayed Jobs. This ensures the job queue is empty

Compare an existing entry that has a wav form image to our local instance

• Open production entry at https://oralhistory.library.ucla.edu/catalog/21198-zz002khbcc in browser
• Import local matching entry in the admin interface, enter 21198-zz002khbcc then click Run Single Import
• Open matching local entry at http://127.0.0.1:8000/catalog/21198-zz002khbcc in browser
• Observe no wav form image in the local instance
• Re-import this specific record in the local admin interface
• Enter 21198-zz002khbcc and click Run Single Import, wait until entry is imported
• Reload the local entry at http://127.0.0.1:8000/catalog/21198-zz002khbcc
• No wav form image will appear, though the audio does exist, as verified by the production entry

[akohler]

@kjallen I've tested this and it does what it should. Confirmed that if local record had a wave form image (for me, imported against the main branch), then re-imported on the new branch, the wave form image was not removed. And if local record had no wave form image, re-importing on the new branch did not change that, it still had no wave form image.

I pushed a commit to flesh out the Linux-specific instructions, and added a "recipe" for connecting to the database via docker-compose, simpler than the instructions you removed.

I'm merging this, then will deploy to stage so you can test it there.