Fix brakeman CI failure by removing --ensure-latest flag and updating to 8.0.4

The --ensure-latest flag in bin/brakeman caused exit code 5 whenever a
newer brakeman version was released, breaking CI. Removing this flag
prevents future failures while still running the bundled version.

Author: rjohnson2011

CLAUDE.md

@@ -7,7 +7,7 @@ Rails 8 API backend for the PR Dashboard application. Tracks pull requests, revi
 
 ### Hosting & Infrastructure
 - **API Server**: Render.com free tier (512MB RAM limit)
-- **Database**: Neon PostgreSQL (serverless, free tier)
+- **Database**: Supabase PostgreSQL (free tier, no compute hour limit)
 - **Cron Jobs**: GitHub Actions (replaced Render cron jobs)
   - Runs every 15 minutes during business hours (Mon-Fri, 6am-6pm PT)
   - Workflow: `.github/workflows/pr-scraper.yml`
@@ -50,7 +50,7 @@ Current version: **5.0** (defined in `app/controllers/api/v1/reviews_controller.
 ## Configuration
 
 ### Environment Variables (on Render)
-- `DATABASE_URL` - Neon PostgreSQL connection string
+- `DATABASE_URL` - Supabase PostgreSQL connection string (Session pooler, port 5432)
 - `GITHUB_TOKEN` - GitHub PAT for API access
 - `GITHUB_OWNER` - Default: `department-of-veterans-affairs`
 - `GITHUB_REPO` - Default: `vets-api`

Gemfile.lock

@@ -83,7 +83,7 @@ GEM
     bigdecimal (3.2.2)
     bootsnap (1.18.6)
       msgpack (~> 1.2)
-    brakeman (8.0.2)
+    brakeman (8.0.4)
       racc
     builder (3.3.0)
     chronic (0.10.2)

bin/brakeman

@@ -2,6 +2,4 @@
 require "rubygems"
 require "bundler/setup"
 
-ARGV.unshift("--ensure-latest")
-
 load Gem.bin_path("brakeman", "brakeman")