Keep Doctor from timing out, or ending conversations prematurely

Allow the doctor to have longer more in-depth conversations, especially when it comes to SQLLite. The doctor in our situation kept "timing out" and resetting. It also ran out of conversation at a prime point for fixing, while investigating crashloop on sqllite - simply stating: the conversation has reached its limit. the doctor needs the capability to have longer, and deeper conversations. It also needs better / deeper knowledge about SQLLite (especially when the WAL gets too large, and there may be thousands of file locks, and tens of thousands of commit issues, failed jobs, etc...) It doesn't have enough knowledge yet to accurately fix the problem, and multiple times requested me to log the case with support.