remove separate codeinsights-db pod in local development and point to…
Created by: coury-clark
Utilize the same primary DB for code insights database. This is the same strategy as code-intel.
Note: we do have some small concerns about discoverability / naming collisions. Ideally we'd separate this into a new database on the same instance, but I don't see any clear way to do that right now without some manual effort involved (either running sg setup
Test plan
It works on my machine