adding diamond version 2.1.17

[erinyoung]

There's a new version of diamond!

I couldn't get the image to build for me in github codespaces, so I'm setting this as a draft for now. I will revisit this later (hopefully), although I won't be offended if someone else beats me to it.

According to the release notes there are some new features.

I copied the files from the prior version and updated the version arg.

The full diff

$ diff ./build-files/diamond/2.1.1{6,7}/Dockerfile
3c3
< ARG DIAMOND_VER="2.1.16"
---
> ARG DIAMOND_VER="2.1.17"
35c35
< RUN wget --quiet --no-check-certificate https://scop.berkeley.edu/downloads/scopeseq-2.07/astral-scopedom-seqres-gd-sel-gs-bib-40-2.07.fa &&\
---
> RUN wget --no-check-certificate https://scop.berkeley.edu/downloads/scopeseq-2.07/astral-scopedom-seqres-gd-sel-gs-bib-40-2.07.fa &&\

Pull Request (PR) checklist:

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