Update HIVdb from version 9.4 to 9.8

Fixes #1407

Changes made:
- Downloaded and integrated HIVdb 9.8 XML (dated 2025-01-05) from Stanford
- Updated resistance.py to use HIVDB_9.8.xml algorithm file
- Updated genreport.yaml with new version 9.8 and date 2025-01-05
- Added DPV (dapirivine) NNRTI drug to genreport.yaml and test expectations
- Updated all test files (test_resistance.py, test_asi_algorithm.py) for version 9.8
- Fixed drug name spelling from 'dapivirine' to 'dapirivine' per HIVdb XML
- Removed obsolete HIVDB_9.0.xml and HIVDB_9.4.xml files
- Added comprehensive update guide in docs/contrib.md
- Created automation script update_hivdb.py for future updates
- Verified pyvdrm v0.3.2 compatibility with HIVdb 9.8

All tests pass:
- 86 tests in micall/tests/test_resistance.py
- 28 tests in micall/tests/test_asi_algorithm.py
- 15 tests in micall/tests/test_genreport.py

Note: CA region (Capsid) drug LEN was intentionally excluded as CA is not
included in get_algorithm_regions() per previous implementation.

Author: Donaim

docs/contrib.md

@@ -139,6 +139,98 @@ docker run \
 # Goto http://localhost:4000
 ```
 
+### Updating HIVdb
+
+When a new version of the Stanford HIV Drug Resistance Database is released,
+follow these steps to update MiCall:
+
+1. **Download the new rules file**: Visit [https://hivdb.stanford.edu/](https://hivdb.stanford.edu/)
+   and download the latest XML algorithm file. The file can typically be found
+   in the algorithm/downloads section or by searching for "ASI XML" or "algorithm XML".
+
+2. **Note the version details**: Record the version number (e.g., 9.8) and the
+   modification date from the XML file or the HIVdb website.
+
+3. **Add the new XML file**: Place the downloaded XML file in `micall/resistance/`
+   with the naming convention `HIVDB_X.X.xml` (e.g., `HIVDB_9.8.xml`).
+
+4. **Update `HIV_RULES_PATH`**: In `micall/resistance/resistance.py`, update
+   the path to point to the new XML file:
+   ```python
+   HIV_RULES_PATH = os.path.join(os.path.dirname(__file__), 'HIVDB_X.X.xml')
+   ```
+
+5. **Update version in genreport**: In `micall/resistance/genreport.yaml`,
+   update the version number and modification date in the `generated_by_text`
+   field (look for "Stanford HIVdb"):
+   ```yaml
+   generated_by_text: >
+     Generated by MiCall {} on Illumina BaseSpace using Stanford HIVdb
+     X.X, modified on YYYY-MM-DD.
+   ```
+
+6. **Handle new drugs** (if applicable): If the new HIVdb version introduces
+   new drugs, add them to the appropriate drug class in `genreport.yaml`.
+   For example, to add a new INSTI drug:
+   ```yaml
+   INSTI:
+     - [BIC, Bictegravir]
+     - [NEW, New Drug Name]  # Add new drug here
+     - [DTG, Dolutegravir]
+   ```
+   Use the format: `[ABBREVIATION, Full Drug Name]`. The order determines how
+   drugs appear in the report.
+
+7. **Check pyvdrm compatibility**: Verify the current pyvdrm version in
+   `pyproject.toml` supports the new HIVdb version. The pyvdrm library parses
+   the HIVdb XML format. If compatibility issues arise:
+   - Check the [pyvdrm repository](https://github.com/cfe-lab/pyvdrm) for updates
+   - Update the version in `pyproject.toml` if needed:
+     ```toml
+     "pyvdrm @ git+https://github.com/cfe-lab/[email protected]"
+     ```
+
+8. **Update tests**: Modify test files to reflect the new version and any
+   algorithm behavior changes:
+   - `micall/tests/test_resistance.py`: Update version number assertions
+   - `micall/tests/test_asi_algorithm.py`: Update expected resistance scores
+     if the algorithm produces different results
+
+9. **Delete old XML files**: Remove old HIVdb XML files from `micall/resistance/`
+   to avoid confusion. Keep only the new version:
+   ```shell
+   rm micall/resistance/HIVDB_9.0.xml
+   rm micall/resistance/HIVDB_9.4.xml
+   ```
+
+10. **Run tests**: Execute the test suite to ensure everything works:
+    ```shell
+    pytest micall/tests/test_resistance.py
+    pytest micall/tests/test_asi_algorithm.py
+    pytest  # Run all tests
+    ```
+
+11. **Manual verification**: Process a sample dataset through the pipeline and
+    review the generated resistance reports to ensure output is correct and
+    formatting is preserved.
+
+12. **Create a pull request**: Document all changes, reference issue #1407 (or
+    the current update request), include test results, and note any behavioral
+    changes in the algorithm.
+
+**Note on CA (Capsid) region**: Some HIVdb versions include the CA region for
+Capsid Inhibitors. If present and not yet supported in MiCall, the region is
+automatically skipped by the `get_algorithm_regions()` function in
+`resistance.py`. Decide whether to add CA support based on clinical needs.
+
+**Troubleshooting**:
+- If tests fail due to changed resistance scores, verify the changes are
+  expected based on HIVdb release notes before updating test assertions.
+- If pyvdrm parsing errors occur, the XML format may have changed. Check for
+  pyvdrm updates or contact the maintainers.
+
+## Making a Release
+
 What changes might you want to make? The web site is based on the
 [Bulma Clean Theme], so read through the documentation there to see if it
 already has the feature you want. Usually, the advanced features require you