Pull pdf parser docker into the master branch

[jkstratford]

Description

This docker parses a cell viability PDF into a tab delimited table.

Dockerfile Structure and Organization:

• [x] Does the Dockerfile build?
• [X] Is tool organized according to Repository Structure?
• [X] Specific base image with a version tag, e.g., FROM ubuntu:20.04 instead of FROM ubuntu.
• [X] Add comments to describe each Dockerfile step.

Metadata

Include the following LABELs:

• [X] LABEL maintainer="Your Name <your.email@rti.org>"
• [X] LABEL description="Short description of the purpose of this image"
• [X] LABEL software-website="https://example.com"
• [X] LABEL software-version="1.0.0"
• [X] LABEL license="https://www.example.com/legal/end-user-software-license-agreement"

File and Resource Management:

• [X] Store scripts, files, and software tools ONLY in /opt.
• [X] Removing tar files after extraction and delete temporary files and caches generated during the build process.
• [X] Ensure sensitive data (e.g., API keys, passwords) is not hardcoded in the Dockerfile.

Container Behavior

• [ ] Specify a meaningful CMD to define how the container should run by default (help message is a good default).

[jaamarks]

1. Add a README.md file with this code. e.g., https://github.com/RTIInternational/biocloud_docker_tools/blob/master/cellranger/v7.2.0/README.md

   • I realize that I forgot to add this as a checkbox in the PR-template. So I will fix that. And also I realize now that the main README for this entire biocloud_docker_tools repo should specify that more explicitly. rn it's stated as "Maintain documentation alongside the Dockerfile, describing how to build, run, and use the image."

2. Remove the extra comments at the top of the Dockerfile – those can probably be transferred over to the README.md that you will create for this tool.

[jkstratford]

I created a README.md file patterned after the example that you provided. Let me know if there is any required content that is missing.