fix: wrap int() conversions in try/except to prevent crashes on bad D…

[amansingh1207]

Problem

Two int() conversions in database.py had no error handling:

• int(row["count"]) at page view query
• int(row["avg_security_score"] or 0) in stats aggregation

If the database contains a corrupt/non-numeric value, these raise
ValueError/TypeError and crash the API endpoint.

Fix

• Wrapped int(row["count"]) in try/except returning 0 on failure
• Added type guard for avg_security_score before conversion

Impact

Prevents unhandled exceptions that could expose internal stack traces
or cause API downtime.

[Stanzin7]

Thanks @amansingh1207 — both lines this edits still exist (database.py:423 and :711), so it would merge, but the crashes it guards against can't occur on current master: get_statistics is already wrapped in try/except Exception (database.py:681-723) and returns safe defaults. Since it guards a non-reachable failure, I'd recommend closing.