Hmmer again

[AbhirupaGhosh]

Description

What kind of change(s) are included?

• Feature (adds or updates new capabilities)
• Bug fix (fixes an issue).
• Enhancement (adds functionality).
• Breaking change (these changes would cause existing functionality to not work as expected).

Checklist

Please ensure that all boxes are checked before indicating that this pull request is ready for review.

• I have read and followed the CONTRIBUTING.md guidelines.
• I have searched for existing content to ensure this is not a duplicate.
• I have performed a self-review of these additions (including spelling, grammar, and related).
• I have added comments to my code to help provide understanding.
• I have added a test which covers the code changes found within this PR.
• I have deleted all non-relevant text in this pull request template.
• Reviewer assignment: Tag a relevant team member to review and approve the changes.

[AbhirupaGhosh]

If you have your favorite bug's duckdb (with protein_cluster_seq table), use that to try
.runHMMER() and .defenseHMMER()

[AbhirupaGhosh]

@epbrenner and @jananiravi, currently, we are not using any cut-off for evalue. The default is E <= 10. I think 1e-3 or a stringency like 1e-5 cut-off would make more sense. Let me know your thoughts.
Otherwise, the PR is again ready for your review.

[epbrenner]

@AbhirupaGhosh Give it a spin with my minor updates to make sure it's running well still on your end, but all basic functionality looks good! All databases install and scan with the primary .runHMMER and .defenseHMMER functions.

[epbrenner]

Approved pending a secondary check by @AbhirupaGhosh of my verbosity and mapping changes in the most recent commit.

[AbhirupaGhosh]

I ran the whole thing again just to check things are in place. Next step is adding HMMer runs to runDataProcessing().