Fix dead logging config: com.javarag package names never match the codebase

[devops-thiago]

Background

The application is configured to enable DEBUG logging for the packages com.javarag and com.javarag.service in src/main/resources/application.yml and src/main/resources/application-docker.yml, but every class in this repository lives under br.com.arquivolivre.myjavagenie (e.g. br.com.arquivolivre.myjavagenie.service.QueryService). The logging settings are therefore dead configuration — they never take effect.

Impact

• Developers debugging the RAG pipeline (retrieval, embedding, generation) cannot get the verbose logging the config advertises.
• Misleading configuration creates a false sense of observability: anyone reading application.yml believes service-level DEBUG logs are on.
• Troubleshooting production issues under the Docker profile is harder than intended.

How to reproduce

1. Start the app with the default profile (or docker profile).
2. Send a query to POST /api/chat/query.
3. Observe that no DEBUG lines from QueryService, RetrievalEngine, or ChromaVectorRepository appear, even though com.javarag.service: DEBUG is set.

Where the fix should land

Replace the com.javarag entries with the real base package br.com.arquivolivre.myjavagenie in both YAML files. Expected result:

logging:
  level:
    root: INFO
    br.com.arquivolivre.myjavagenie: INFO
    br.com.arquivolivre.myjavagenie.service: DEBUG
    br.com.arquivolivre.myjavagenie.repository: DEBUG
    dev.langchain4j: WARN

Keep the root and dev.langchain4j levels as-is.

Files touched

• src/main/resources/application.yml
• src/main/resources/application-docker.yml

Acceptance criteria

• Both YAML files reference br.com.arquivolivre.myjavagenie with no com.javarag remnants.
• Running with DEBUG for the service package emits DEBUG lines from QueryService/RetrievalEngine on a live query.
• mvn test and mvn spotless:check pass.