Update PeptideShaker recipe to 3.0.13

[BioGeek]

This PR updates the Bioconda peptide-shaker recipe to the PeptideShaker release that contains the merged InstaNovo import and no-FASTA de novo project support.

The PeptideShaker integration depends on the Compomics Utilities and PeptideShaker PRs being merged and released first.

Changes

• Updates the PeptideShaker version.
• Updates the source checksum.
• Updates the wrapper script jar filename.
• Updates package description text to mention de novo workflows including InstaNovo, InstaNovo+, and InstaNovo with refinement.

Merge Order

Recommended order:

1. Add InstaNovo and InstaNovo+ import support CompOmics/compomics-utilities#73
2. Add SearchGUI support for InstaNovo and InstaNovo+ CompOmics/searchgui#387
3. Add PeptideShaker import UI support for InstaNovo result files CompOmics/peptide-shaker#570
4. Add DeNovoGUI compatibility APIs to Utilities CompOmics/compomics-utilities#74
5. Add InstaNovo support to DeNovoGUI CompOmics/denovogui#53
6. Update SearchGUI recipe to 4.3.17 #66604
7. This PR
8. Expose InstaNovo workflows in online input form barsnes-group/peptide-shaker-online#30
9. Bump PeptideShaker wrappers for InstaNovo support galaxyproteomics/tools-galaxyp#828

---

Please read the guidelines for Bioconda recipes before opening a pull request (PR).

General instructions

• If this PR adds or updates a recipe, use "Add" or "Update" appropriately as the first word in its title.
• New recipes not directly relevant to the biological sciences need to be submitted to the conda-forge channel instead of Bioconda.
• PRs require reviews prior to being merged. Once your PR is passing tests and ready to be merged, please issue the @BiocondaBot please add label command.
• Please post questions on Gitter or ping @bioconda/core in a comment.

Instructions for avoiding API, ABI, and CLI breakage issues

Conda is able to record and lock (a.k.a. pin) dependency versions used at build time of other recipes.
This way, one can avoid that expectations of a downstream recipe with regards to API, ABI, or CLI are violated by later changes in the recipe.
If not already present in the meta.yaml, make sure to specify run_exports (see here for the rationale and comprehensive explanation).
Add a run_exports section like this:

build:
  run_exports:
    - ...

with ... being one of:

Case	run_exports statement
semantic versioning	{{ pin_subpackage("myrecipe", max_pin="x") }}
semantic versioning (0.x.x)	{{ pin_subpackage("myrecipe", max_pin="x.x") }}
known breakage in minor versions	{{ pin_subpackage("myrecipe", max_pin="x.x") }} (in such a case, please add a note that shortly mentions your evidence for that)
known breakage in patch versions	{{ pin_subpackage("myrecipe", max_pin="x.x.x") }} (in such a case, please add a note that shortly mentions your evidence for that)
calendar versioning	{{ pin_subpackage("myrecipe", max_pin=None) }}

while replacing "myrecipe" with either name if a name|lower variable is defined in your recipe or with the lowercase name of the package in quotes.

Bot commands for PR management

Please use the following BiocondaBot commands:

Everyone has access to the following BiocondaBot commands, which can be given in a comment:

@BiocondaBot please add label	Add the please review & merge label.
@BiocondaBot please fetch artifacts	Post links to CI-built packages/containers. You can use this to test packages locally.

Note that the @BiocondaBot please merge command is now depreciated. Please just squash and merge instead.

Also, the bot watches for comments from non-members that include @bioconda/<team> and will automatically re-post them to notify the addressed <team>.