Remove SQLite production warning but leave production config disabled

[byroot]

Fix: #49715

There are valid use cases for running SQLite in production, however it must be done with care, so instead of a warning most users won't see anyway, it's preferable to leave the configuration commented out to force them to think about having the database on a persistent volume etc.

Co-Authored-By: @intrip

[northeastprince]

Suggested change

	# database: path/to/persistent/storage/production.sqlite3
	# database: storage/production.sqlite3

I think just commenting it out is fine since most would probably use the default storage folder anyway, but persisted with something like Docker volumes.

[dhh]

This feels like a good compromise. But also wonder if we should support passing in a path using DATABASE_URL in production?

[byroot]

if we should support passing in a path using DATABASE_URL in production?

Makes sense to me but is orthogonal. Best handled in another PR.

[dhh]

Yeah I guess DATABASE_URL overwrites in any case. Looks good to me then 👍

[skipkayhil]

Looks like rails-new-docker is correctly failing because it uses a sqlite3 db and now has no production configuration. Maybe it should be changed to one of the others?

[byroot]

I think I'll squeeze the DATABASE_URL support to fix it...

[byroot]

Actually it's already supported.