fix(engine_function): sanitize ANSI escapes in Prisma severity parsing

[cjrdz]

Description

This PR fixes an issue where ANSI escape/control sequences from Prisma/Twistcli output leaked into parsed vulnerability severity values (for example, \x1b[31;1Mcritical). As a result, severity normalization and downstream payload validation could fail in pipeline executions.

The fix adds robust ANSI sanitization during function-scan parsing and normalizes severity values before findings are built, ensuring valid outputs critical/high/medium/low are consistently produced.

Fix

To fix in code/runtime

• Sanitize scanner text output before field extraction so terminal color/control bytes are removed.
• Normalize severity values with strip + lower + mapping before building findings.

Checklist:

• The pull request is complete according to the guide of contributing of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my feature, policy, or fix is effective and works
• New and existing tests pass locally with my changes

[app-toolkit-opensource-innersource]

🎉 This PR is included in version 1.144.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀