Fix failing Debian test case for mini-httpd

[yashkohli88]

Description

During our CI runs, the Debian test case for mini-httpd/1.30-0.2 has been failing.
See the failing workflow:
https://github.com/clearlydefined/operations/actions/runs/16382766911/job/46297303976

Error message:

Debian: got 0 entries for cd:/debsrc/debian/-/mini-httpd/1.30-0.2

Cause

The version (1.30-0.2) for mini-httpd used in our test suite is no longer available in the Debian package repo.
See: http://ftp.debian.org/debian/pool/main/m/mini-httpd/

### Resolution
There are newer versions (e.g., 1.30-2 and above) available. This PR updates the test config to use a currently available version to restore CI pass (successful harvest).

### Checklist

• Update test configuration to use mini-httpd/1.30-13
• Confirm tests now pass in CI

[qtomlinson]

@jamesiri As per our discussion on harvest failures during integration tests.

[qtomlinson]

@jamesiri The harvests are now successful. See logs

The definition comparison failed for the following components:

• https://api.clearlydefined.io/definitions/conda/conda-forge/linux-aarch64/numpy/1.16.6-py36hdc1b780_0,
• https://api.clearlydefined.io/definitions/pypi/pypi/-/sdbus/0.12.0,
• https://api.clearlydefined.io/definitions/deb/debian/-/mini-httpd/1.30-13_armhf,

Example difference:

-------------------
expected: {"path":"lib/python3.6/site-packages/numpy/distutils/cpuinfo.py","license":"BSD-3-Clause","attributions":["Copyright 2002 Pearu Peterson"],"hashes":{"sha1":"d4175e6d6804f6ef973f4a655d2e10499d239033","sha256":"00726e41e83bf3f3f911178ed642ddf8c02886f07e19f57ccee461ec5f2196d2"}}
actual:   {"path":"lib/python3.6/site-packages/numpy/distutils/cpuinfo.py","license":"BSD-3-Clause AND BSD-2-Clause AND (BSD-3-Clause AND Python-2.0 AND Apache-2.0)","attributions":["Copyright 2002 Pearu Peterson"],"hashes":{"sha1":"d4175e6d6804f6ef973f4a655d2e10499d239033","sha256":"00726e41e83bf3f3f911178ed642ddf8c02886f07e19f57ccee461ec5f2196d2"}}
-------------------

These need to be inspected and likely due to the changes in license detection in the newer version of ScanCode. If these changes are valid, we can update the fixtures.