Persist model_version and ruleset_version in feedback records

[Th-Shivam]

Summary :

The feedback API currently saves model_version and ruleset_version as None, which makes auditability and analytics harder.

Reference: main.py (line 2216)

Expected :

When feedback is submitted, the API should persist the correct model_version and ruleset_version from the related scan result metadata.

Why it matters

This helps us:

track feedback against the exact scan context
improve auditing
support future model/ruleset comparisons
Acceptance Criteria
model_version and ruleset_version are no longer hardcoded to None
values are extracted from scan metadata when available
missing metadata is handled safely
tests cover the new behavior

[Stanzin7]

@sapnilbiswas can you review this. This has conflicts with the main.py

[sapnilbiswas]

@Stanzin7 It looks good enough; the issue is apt and the PR creates conflicts with main.py but majorly they are positional shifts.

[sapnilbiswas]

@Th-Shivam, can you please check your PR #47 once and rectify the failed CI jobs so we can proceed with merging