Fix: Add backward-compatible handling for missing score column in parsecdCache module

[katon1731367]

Description

This pull request improves the parsecdCache.py artifact parser by adding backward-compatible handling for older ParseCD Cache databases that do not contain the score column.
The updated logic dynamically inspects table schema via PRAGMA table_info and safely substitutes NULL AS score when the column is absent. This prevents SQLite errors when processing legacy datasets.

Errors Encountered

When running iLEAPP against the 2020 CTF – iOS dataset, the following error occurred:

It originated from the completion_cache_engagement table, which lacks the score field in older iOS datasets.

Dataset to Reproduce

Source: 2020 CTF – iOS forensic dataset (EngagedCompletions/Cache.db)

Relevant table: completion_cache_engagement

Issue: Table schema does not include the score column

Running get_parseCDCache on this dataset reliably reproduces the error.

The Fix

• Added a schema check using PRAGMA table_info(completion_cache_engagement);
• If score exists, it is selected normally.
• If not present, the query uses NULL AS score to preserve output format.
• Ensures output headers remain consistent regardless of dataset version.
• No changes to downstream code or artifact structure.
• This provides full backward compatibility with older ParseCD Cache databases.

Verification (Before/After)

Before Fix:
iLEAPP aborts artifact processing with sqlite3.OperationalError: no such column: score
No report generated for this artifact.

After Fix:
Artifact runs without errors.

Rows from older ParseCD Cache files are parsed successfully.
The “Score” column is populated with NULL for datasets that lack the field.
Output verified using the 2020 CTF – iOS Cache.db dataset.