ENV boolean fields should not be strings

When reading from the .env file, all boolean values, `True`, `False` are automatically type-cast to strings by python. Initially the application was architected to just handle them as strings, but this is not ideal for future maintainability and extension of features.

This architecture should be revised so that they are truly booleans in the application logic and not string encapsulations of boolean values.

No files or tests are named in the issue. Start by finding where the app reads `.env` values and maps them into configuration or application settings. Trace how boolean-like flags are currently consumed so you can adjust the parsing path to preserve real booleans in logic instead of string values. You’re done when config loading consistently yields typed booleans for those fields and the project’s tests/checks for env/config behavior pass.

Scritto dal modello di indicizzazione a partire dal testo della issue.