adding blast verion 2.15.0

[erinyoung]

I copied the Dockerfile for blast/2.14.1 and made the following changes:

• updated the base to jammy
• changed BLAST_VER to "2.15.0"

Changes in 2.15.0 according to https://www.ncbi.nlm.nih.gov/books/NBK131777/:

BLAST+ 2.15.0: October 31, 2023
New features
You can limit your search by a non-leaf taxID (e.g., all bacteria) without running a helper script.
BLAST now selects the best threading mode (i.e., sets -mt_mode option) based on your query and database for BLASTN, BLASTP, BLASTX, and TBLASTN.
Improvements
Optimized batch size for blastx-fast for smaller databases (e.g., Swiss-Prot) and many queries to make it 7% faster.
Improved the error message shown if the LMDB file (part of BLAST database) cannot be opened (mentions file).
update_blastdb.pl will use at most 25% of the CPUs on a machine when downloading from the cloud (adjustable with an option).
Bug fixes
Fixed a megaBLAST crash in two-hit mode.
Fixed a TBLASTN crash with very short database sequences and a taxonomy limit.

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/samtools/1.15 )
• 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)
  • (optional) All test files are located in same directory as the Dockerfile (i.e. shigatyper/2.0.1/test.sh)
• Create a simple container-specific README.md in the same directory as the Dockerfile (i.e. 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

[erinyoung]

Closes #779

[Kincekara]

Thank you for your contribution!
You can check your image deployment from https://github.com/StaPH-B/docker-builds/actions/runs/7248930636.