Add logging and validation improvements

[avalonche]

📝 Summary

Some logging improvements and validation:

• Logging error only if the bid was eligible and payload was not found. failed getting execution payload (2/2) - payload not found, but found bid in database - this error log occurred often due to race conditions in which a submission passed checkFloorBidValue earlier in the request and was simulated. However a higher value bid was simulated and updated in redis before the block submission finished simulation, resulting in a bid below the floor when SaveBidAndUpdateTopBid is reached. The bid is saved but the payload was not.
• Demote the 202 response code to a warning. This response code was returned from lighthouse when a duplicate block was gossiped, see [Merged by Bors] - Send success code for duplicate blocks on HTTP sigp/lighthouse#4655
• Changes the data api parameters to int64. bigint in postgres is represented as a int64 value which was not properly validated in the request parameters and uint64 values could be inputted.

⛱ Motivation and Context

Reduces error logging noise in the relay.

📚 References

---

✅ I have run these commands

• make lint
• make test-race
• go mod tidy
• I have seen and agree to CONTRIBUTING.md

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 17 lines in your changes are missing coverage. Please review.

Project coverage is 30.41%. Comparing base (108d5e3) to head (82adb09).

Files	Patch %	Lines
services/api/service.go	0.00%	13 Missing ⚠️
beaconclient/multi_beacon_client.go	0.00%	4 Missing ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #589      +/-   ##
==========================================
- Coverage   30.44%   30.41%   -0.03%     
==========================================
  Files          41       41              
  Lines        6268     6273       +5     
==========================================
  Hits         1908     1908              
- Misses       4113     4118       +5     
  Partials      247      247              

Flag	Coverage Δ
unittests	30.41% <0.00%> (-0.03%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[metachris]

lgtm. left a small comment and not sure why changing uint to int?

[avalonche]

postgres bigint uses int64, and the error occurs when user input larger than int64 is entered. Changing from uint64 to int64 would bound the values to int64, the same representation as Postgres and the error will be handled in ParseInt instead of checking for the bound ourselves