Upgrade OpenGrep 1.16.4

[DMarinhoCodacy]

No description provided.

[codacy-production]

Codacy's Analysis Summary

0 new issue (≤ 0 minor issue)
0 new security issue
0 complexity
0 duplications
More details

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes. Give us feedback}

[codacy-production]

Pull Request Overview

While the PR aligns with the goal of upgrading OpenGrep, the implementation of the syntax error detection contains a logic flaw that will likely prevent it from functioning correctly for long error messages. Furthermore, the PR introduces significant logic changes to command execution and error handling without any accompanying unit tests to verify the new flags or the error parsing logic. The addition of 'test.c' appears to be unused noise in the codebase as it is not referenced by any tests or the Dockerfile.

About this PR

• Significant logic changes were made to command execution parameters and error handling logic without accompanying unit tests in the diff.
• The file 'test.c' was added but is not referenced or used by any automated test or process in the pull request.
• The PR lacks a description and Jira ticket reference, making it difficult to verify the full scope of changes beyond the title.

Test suggestions

• Verify that the opengrep command is constructed with the correct flags: -l, --error-recovery, -j, and -fast.
• Verify that a Semgrep error containing 'Syntax error at line' is converted to 'The file could not be parsed, likely due to syntax errors.'
• Verify that error messages not related to syntax are still passed through (truncated to 250 chars).

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify that the opengrep command is constructed with the correct flags: -l, --error-recovery, -j, and -fast.
2. Verify that a Semgrep error containing 'Syntax error at line' is converted to 'The file could not be parsed, likely due to syntax errors.'
3. Verify that error messages not related to syntax are still passed through (truncated to 250 chars).

---

🗒️ Improve review quality by adding custom instructions