Log section for test on generated apps isn't very useful

Nobody has claimed this yet.

When you generate a new app, you get this section in your `config/log.cr` file

https://github.com/luckyframework/lucky_cli/blob/8344b2749c8cadc560312a4cfc6499275815377c/src/web_app_skeleton/config/log.cr.ecr#L3-L11

This used to be very helpful because back in the day when specs would run, you had a full HTTP server that booted, and you could tail this file to watch the logs and see what was going on. However, that's not the case anymore because booting an HTTP server on spec run is expensive and slow.

This leads to an issue where you run your specs, and you get a 500 error in an action, and tailing this log just looks like this


We need to figure out how we can rework this so your queries and errors and everything can go to this file and not STDOUT to the terminal. You should be able to tail this file while running specs and get good information as to what queries your spec is running and what exceptions or errors you're hitting.

Start with src/web_app_skeleton/config/log.cr.ecr and compare the generated logging configuration with how specs currently emit queries, exceptions, and errors. Run the generated app's specs and verify that tailing the configured log file shows useful query and error information instead of relying on STDOUT.

Written by the indexing model from the issue text.