Support Loopback 4

[timokoessler]

Summary by Aikido

Security Issues: 0	🔍 Quality Issues: 4	Resolved Issues: 0

🚀 New Features

• Added LoopBack integration with body parsing and route parameter handling

⚡ Enhancements

• Enabled callback-on-block handling for interceptors and added helper utility

^{More info}

[codecov]

Codecov Report

❌ Patch coverage is 97.27891% with 4 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
library/sources/LoopBack.ts	96.22%	3 Missing and 1 partial ⚠️

📢 Thoughts on this report? Let us know!

[aikido-pr-checks]

Top-line comment restates the function's behavior. Remove it or replace with a brief explanation of why finding the last callback is necessary for callers.

Suggested change

	// Finds the last function argument in the provided array and returns it. If no function is found, it returns undefined.
	// Extracts the callback from variadic arguments to support Node.js APIs that accept an optional callback as the last parameter.

Details

✨ AI Reasoning
​A comment was added that simply restates the implementation: it describes iterating arguments to find the last function and returning undefined otherwise. This provides no design rationale or higher-level context and thus is a 'what' comment that increases maintenance burden.

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