fix: Update GET proof record endpoint to return 404 for non-existing records

[amrrdev]

Issue Fixed:
I addressed the error handling in the proof record retrieval endpoint where it was returning a 500 status code for non-existing records. The issue was in the verification service's error handling logic.

Changes Made:

1. Modified error handling in verification.service.ts for the getProofPresentationById method
2. Updated the error detection to properly identify "record not found" cases
3. Implemented proper 404 response using NestJS's NotFoundException
4. Maintained the original error message for clarity

Before:

• API returned 500 status code with a generic error
• Error structure was inconsistent with API standards
• Generic "Something went wrong!" message wasn't helpful

After:

• API now returns 404 status code for non-existing records
• Clear error message indicates the specific proofId that wasn't found
• Consistent error structure throughout the API
• Better error handling helps client applications handle missing records appropriately

This change improves the API's error handling consistency and provides better feedback for client applications trying to access non-existing proof records.

[GHkrishna]

Thank you for the PR @amrrdev

I've left some comments and requested a review from @bhavanakarwade

Also, in the meantime can you please check DCO since it seems to be failing

[GHkrishna]

Looks good to me just requesting some minor changes

[GHkrishna]

Thank for the contribution and for your patience @amrrdev

[GHkrishna]

Some of your commits don't seem to be verified, can you please check them once?

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[amrrdev]

@GHkrishna, I have verified the commit.

[GHkrishna]

That's great, thank you for your contribution!

[bhavanakarwade]

@amrrdev, Thank you for your patience and contribution.