fix: tighten audit log count assertion in integration test

[DivyashreeR008]

Summary

Fixes #51 -- The audit log count assertion used -ge 0, which can never fail because every non-negative integer (including 0) satisfies it. Combined with 2>/dev/null, even a completely empty or failed response would silently pass.

Root Cause

Line 402 in run-integration-tests.sh:

if [ "$AUDIT_COUNT" -ge 0 ] 2>/dev/null; then

Three problems:

1. -ge 0 is always true for any non-negative integer (0, 1, 42, etc.)
2. 2>/dev/null hides bash errors if $AUDIT_COUNT is empty or not a number
3. On parse failure, AUDIT_COUNT defaults to "0", which still satisfies -ge 0

The assertion was mathematically incapable of failing.

Changes

Before	After
-ge 0	-gt 0 (requires at least 1 entry)
2>/dev/null suppressed errors	Removed to surface parse failures
report_fail (soft failure, test continues)	exit 1 (hard failure, stops the suite)
Generic pass/fail message	Clear message showing actual count

The integration test suite will now correctly fail if the audit service stops recording logs, preventing silent audit compliance gaps.

[DivyashreeR008]

Thanks for the review. Confirmed the CI failures (notification-go-service, auth-service docker builds) are pre-existing and unrelated to this change -- this PR only touches the shell assertion logic in
un-integration-tests.sh.

[Senthil455]

gh: Not Found (HTTP 404)
{"message":"Not Found","documentation_url":"https://docs.github.com/rest/issues/comments#get-an-issue-comment","status":"404"}