Switch PANTHER trees to version 19.0

[dustine32]

The official ticket for switching pipeline components to PANTHER 19.0 (from 17.0). Tested in geneontology/go-site#2364.

• Update PANTHER_VERSION in Jenkinsfile. Update PANTHER_VERSION to 19.0 #400
• Update metadata/go-reference-species.yaml in go-site to reflect new 19.0 species. Update go-reference-species.yaml for PANTHER19.0 go-site#2372
• Swap symlink on data.pantherdb.org to point to latest 19.0 IBA GAFs

[dustine32]

Speaking with @kltm yesterday, I will PR the PANTHER_VERSION change into Jenkinsfile on all 6 of these relevant branches:

• master - PR: Update PANTHER_VERSION to 19.0 #400
• snapshot - PR: Update snapshot Jenkinsfile for #399 #401
• snapshot-post-fail - PR: Update snapshot-post-fail Jenkinsfile for #399 #402
• release - PR: Update release Jenkinsfile for #399 #403
• derivatives-from-goa - PR: Update derivatives-from-goa Jenkinsfile for #399 #404
• go-raw-data - PR: Update go-raw-data Jenkinsfile for #399 #405

After merging these PRs into their branches I will scan repository on build to flush the changes so they don't run automatically.

[dustine32]

Merged all six Jenkinsfile PRs and scanned repository and aborted all launched runs. I then deleted the PR branches so they no longer would show on the Jenkins build UI.

With the go-site/metadata/go-reference-species.yaml PR merged and pantherftp symlink switched, everything should be in place for the next snapshot run.

[kltm]

@dustine32 @pgaudet Noting that we should now have PANTHER 19 propagated through snapshot.