Refactor IP allowance checks in request processing

[tudor-timcu]

Summary by Aikido

Security Issues: 0	🔍 Quality Issues: 1	Resolved Issues: 0

🔧 Refactors

• Refactored endpoint IP allowance checks and improved blocked logging
• Removed unused utils import from request context module

^{More info}

[aikido-pr-checks]

GetEndpointIpAllowed suggests a boolean result but returns an int status. Rename to indicate it returns a status (e.g., GetEndpointIpAllowedStatus) or change it to return a boolean for clarity.

Details

✨ AI Reasoning
​A function was added/renamed whose identifier implies a boolean "allowed" check but its actual return type is an int status code. This mismatch can confuse callers and future maintainers about expected semantics; a clear name should indicate that it returns a status value instead of a boolean, or the function should return a boolean. The change affects cross-function usage and alters the contract of endpoint-IP checks.

🔧 How do I fix it?
Use descriptive names for variables (except standard loop counters i, j, k and math variables x, y).

_{Reply @AikidoSec feedback: [FEEDBACK] to get better review comments in the future.
Reply @AikidoSec ignore: [REASON] to ignore this issue.
More info}