fix(deps): bump accuknox-sq-sast to 2.0.3 (aiohttp py3.9 fix)

[Vickydew1]

Problem

accuknox-sq-sast 2.0.2 hard-pinned aiohttp==3.14.3, which requires
Python >=3.10. That broke pip install accuknox-aspm-scanner (and
pipenv install, outside the pinned 3.10 interpreter) on any Python
3.9 environment — notably Amazon Linux 2023, whose default system
python3 is 3.9. pip filtered every 3.14.x aiohttp release out of
the candidate list there:

ERROR: Could not find a version that satisfies the requirement aiohttp==3.14.3 (from accuknox-sq-sast)
ERROR: No matching distribution found for aiohttp==3.14.3

even though the version exists on PyPI — it's just incompatible with
the running interpreter.

Fix

accuknox-sq-sast 2.0.3 relaxes that to aiohttp>=3.9,<4 (see
accuknox/aspm-sastjob#13),
so pip resolves whichever build matches the caller's interpreter:
aiohttp 3.13.x on Python 3.9, 3.14.x on Python 3.10–3.14.

Updated both places that reference the wheel:

• Pipfile (pipenv/pyinstaller build path)
• setup.cfg (the pip-installable accuknox-aspm-scanner package, which declares python_requires>=3.9)

Regenerated Pipfile.lock accordingly (only the sq-sast entry + lock hash changed — every other resolved version is untouched).

Rechecked every other pinned dependency (pydantic/pydantic-core, colorama, requests, async-timeout, pre-commit) against PyPI's requires_python + wheel tags for Python 3.9–3.14 — no other gaps found.

Verification

pip download --no-deps --python-version 39 --implementation cp --abi cp39 \
  --platform manylinux2014_x86_64 "aiohttp>=3.9,<4"
# -> resolves aiohttp-3.13.5-cp39 (previously: no candidate for aiohttp==3.14.3)

🤖 Generated with Claude Code