[aikido-autofix]

Which Linear task belongs to this PR?

Why did I implement it this way?

This patch mitigates potential file inclusion attacks via path traversal in the deployment utility functions by implementing path validation checks that ensure resolved file paths remain within their intended base directories ('deployments' directory for 'getContractNameFromNetworkDeployments' function and 'cacheDir' for 'DeploymentCache.getMetadataFilePath' method) before performing file read operations, rejecting paths containing parent directory references or absolute paths.

AI Confidence Level (confidence in the quality of this automated fix): Medium confidence: Aikido has validated similar fixes and observed positive outcomes. Validation is required.

Checklist before requesting a review

• I have performed a self-review of my code
• This pull request is as small as possible and only tackles one problem
• I have added tests that cover the functionality / test the bug
• For new facets: I have checked all points from this list: https://www.notion.so/lifi/New-Facet-Contract-Checklist-157f0ff14ac78095a2b8f999d655622e
• I have updated any required documentation

Checklist for reviewer (DO NOT DEPLOY and contracts BEFORE CHECKING THIS!!!)

• I have checked that any arbitrary calls to external contracts are validated and or restricted
• I have checked that any privileged calls (i.e. storage modifications) are validated and or restricted
• I have ensured that any new contracts have had AT A MINIMUM 1 preliminary audit conducted on by <company/auditor>

[0xDEnYO]

Closing: wrong repo for this fix. Every file this PR touches is byte-identical to lifinance/contracts main — synced upstream content with zero Tron-fork delta, so a fix here does not fix upstream and is clobbered by the next syncUpstreamContracts run. Aikido scans this fork as an independent repo and duplicates upstream findings here. If the finding warrants hardening it belongs in lifinance/contracts (cf. merged lifinance#2143) and reaches this fork via sync.