fix(typestate): Prevent false positives on Array.prototype.find()

Remove generic `.find(` from JavaScript/TypeScript database query patterns
since it conflicts with `Array.prototype.find()`. Add more specific ORM
patterns instead:

- `.findById(`, `.findUnique(`, `.findFirst(` (Prisma)
- `.findByPk(`, `.findOrCreate(` (Sequelize)
- `.insertMany(`, `.updateMany(`, `.deleteMany(` (MongoDB)
- `.bulkCreate(` (Sequelize)
- `collection.find(` (explicit MongoDB collection access)

This fixes false positives where `addresses.find(a => a.isDefault)` was
incorrectly flagged as "Query executed without establishing connection".

Co-Authored-By: Claude Opus 4.5 <[email protected]>

Author: bumahkib7

crates/analyzer/src/security/typestate_rules.rs

@@ -2848,22 +2848,35 @@ impl DatabaseStateMachine {
                 ".query(",
                 ".execute(",
                 ".run(",
-                ".find(",
+                // Note: .find( is NOT included because it conflicts with Array.prototype.find()
+                // Use more specific ORM patterns instead
                 ".findOne(",
                 ".findMany(",
+                ".findById(",
+                ".findUnique(",
+                ".findFirst(",
                 ".insertOne(",
+                ".insertMany(",
                 ".updateOne(",
+                ".updateMany(",
                 ".deleteOne(",
+                ".deleteMany(",
                 ".aggregate(",
                 ".exec(",
                 // Sequelize
                 ".findAll(",
+                ".findByPk(",
+                ".findOrCreate(",
                 ".create(",
+                ".bulkCreate(",
                 ".update(",
                 ".destroy(",
                 // Prisma
                 ".$queryRaw(",
                 ".$executeRaw(",
+                // MongoDB specific (collection methods)
+                "collection.find(",
+                ".collection(",
             ],
             begin_patterns: vec![
                 ".beginTransaction(",