adding pango_aliasor version 0.3.0

[erinyoung]

pango_aliasor is not new to the community, but it is new to docker-builds.

pango_aliasor takes pangolin lineages, such as P.1.12.1, and translates them back to their parental lineage, which would be B.1.1.28.1.12.1 for P.1.12.1.

pango_aliasor updates about as frequently as Freyja, meaning that official version updates are few, but the alias key is constantly being updated. When this gets merged into the repository, I'd like to set up a github action like Freyja in order to keep the alias key current.

pango_aliasor is a python package without a real executable on the command line. As such, I've added a script (aliasor.py) that I use in house - because that makes life easy for me.

Pull Request (PR) checklist:

• [X] Include a description of what is in this pull request in this message.
• [X] The dockerfile successfully builds to a test target for the user creating the PR. (i.e. docker build --tag samtools:1.15test --target test docker-builds/samtools/1.15 )
• [X] Directory structure as name of the tool in lower case with special characters removed with a subdirectory of the version number (i.e. spades/3.12.0/Dockerfile)
  • [X] (optional) All test files are located in same directory as the Dockerfile (i.e. shigatyper/2.0.1/test.sh)
• [X] Create a simple container-specific README.md in the same directory as the Dockerfile (i.e. spades/3.12.0/README.md)
  • [X] If this README is longer than 30 lines, there is an explanation as to why more detail was needed
• [X] Dockerfile includes the recommended LABELS
• [X] Main README.md has been updated to include the tool and/or version of the dockerfile(s) in this PR
• [X] Program_Licenses.md contains the tool(s) used in this PR and has been updated for any missing

[Kincekara]

Thank you for putting all these together! Deploy link: https://github.com/StaPH-B/docker-builds/actions/runs/10319938717