Python fp and docs updtes (#58)

* refactor: Update comments for clarity and add expectations.json files for performance metrics

* feat: Implement FP guard for JS/TS local-collection receivers to suppress missing ownership checks

* feat: Enhance Rust parameter handling to classify local collections and prevent false ownership checks

* refactor: Simplify code formatting for better readability in multiple files

* refactor: Improve UTF-8 sequence length handling and enhance clarity in loop iteration

* feat: Update Java and Python patterns to include new security rules

* refactor: Improve comment clarity and consistency across multiple Rust files

* refactor: Simplify code formatting for improved readability in integration tests and module files

* refactor: Improve comment formatting and enhance clarity in assertions across multiple files

tests/fixtures/async_rust/main.rs

@@ -1,7 +1,7 @@
 // Regression fixture: Rust async flow through `tokio::process::Command`.
 //
 // Per docs/language-maturity.md, Rust's Tokio process variants are not
-// yet covered — the Tokio async process APIs are a known gap.  The
+// yet covered, the Tokio async process APIs are a known gap.  The
 // fixture is checked in so that when Rust async-process coverage lands,
 // the engine begins producing the intended finding and the
 // `forbidden_findings` assertion forces whoever adds the coverage to