Clearer container limit info

[ArneTR]

Greptile Overview

Greptile Summary

This PR refactors container information display by introducing a dedicated "Containers" tab and renaming usage_scenario_dependencies to container_dependencies for better clarity. The changes include database schema updates through migrations, frontend UI reorganization with a new tab, and backend data storage modifications.

The refactoring separates container metadata (ID, name, CPU/memory limits) from dependency information, improving the user experience by organizing related information in dedicated UI sections. The changes span across database schema, scenario runner logic, frontend display components, and test files to maintain consistency.

Critical Issues Found:

• XSS Vulnerability: Frontend code inserts container data into HTML without proper escaping, creating a security vulnerability where malicious container data could execute arbitrary JavaScript
• Logic Error: Arithmetic operations on mem_limit field that can be either a string ("1G") or integer (bytes), potentially resulting in NaN values when displaying memory information
• Unit Display Mismatch: Code converts bytes to MB while displaying "MB" label, but the conversion formula suggests GB calculation

Confidence Score: 2/5 - While the refactoring improves code organization, the critical security vulnerability and logic errors require immediate attention before merging.

[ArneTR]

@greptileai

[greptile-apps]

_{10 files reviewed, 3 comments}

_{Edit Code Review Agent Settings | Greptile}

[ArneTR]

@greptileai

[greptile-apps]

_{11 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

syntax: typo: 'explicitly' is misspelled as 'explicitely'

Suggested change

	containers jsonb, -- explicitely not null as entry in runs table gets created first. then filled. so NULL is different info than {}
	containers jsonb, -- explicitly not null as entry in runs table gets created first. then filled. so NULL is different info than {}