Add memory usage check to GitHub Actions workflow

[Hashara]

No description provided.

[bqminh]

change memory-arg and runtime-arg to column name instead of column ID, easier to read and more general.
Use 'real' time to measure wall-clock time, not user time or log file of iqtree.
Document verify_runtime.sh and verify_memory.sh, what arguments do they take as input.

[Copilot]

Pull Request Overview

This PR integrates memory usage checks into the existing CI workflows alongside runtime checks.

• Adds verify_memory.sh and verify_memory.ps1 scripts to validate peak memory against thresholds.
• Refactors verify_runtime.sh/.ps1 and test runners (test_iqtree.sh/.ps1) to log both real time and memory.
• Updates .github/workflows/ci.yaml to invoke memory verification for each build matrix entry.

Reviewed Changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
test_scripts/verify_runtime.sh	Refactored shell runtime check to use named columns and combine logs.
test_scripts/verify_runtime.ps1	Updated PowerShell runtime verification to use column names.
test_scripts/verify_memory.sh	New shell script to verify memory usage against thresholds.
test_scripts/verify_memory.ps1	New PowerShell script for memory verification.
test_scripts/test_iqtree.sh	Enhanced shell test runner to log both runtime and peak memory.
test_scripts/test_iqtree.ps1	Added Measure-IQTree function to capture time and memory in PowerShell.
test_scripts/test_data/expected_runtime.tsv	Added expected runtime threshold data.
test_scripts/test_data/expected_memory.tsv	Added expected memory threshold data.
.github/workflows/ci.yaml	Modified CI to run memory checks after runtime verification.

Comments suppressed due to low confidence (2)

test_scripts/test_iqtree.sh:19

• [nitpick] The local variable USER shadows the environment variable of the same name. Renaming it to something like USER_CPU would improve clarity.

    local REAL USER SYS PEAK_MEM MEM_MB

test_scripts/test_iqtree.ps1:78

• The backtick-quote escaping around -m \"MIX{...}\" seems mismatched and can cause a PowerShell parse error. Consider wrapping the entire command in single quotes or using a here-string to avoid complex escaping.

Measure-IQTree "./build/iqtree3 -s test_scripts/test_data/turtle.fa -m `"MIX{GTR+FO,GTR+FO}`" --link-exchange-rates --prefix test_scripts/test_data/turtle.mix.link -seed $SEED -T 1"

[bqminh]

thanks!