Clarify that marking certain member variables const can hinder performance

In the 03-Style document, I read the following sentence:

> If the member variable is not expected to change after the initialization, then mark it const.

However, we know that if, for example, we mark a container as `const`, we prevent it from being moved, possibly hindering performance. Marking fields as `const` is useful to enforce invariants; however, it "interferes" with performance. If both const correctness and performance are important, one could leave the field non-const, make it private and define a field getter.

Comienza localizando el documento 03-Style y revisando la orientación citada sobre marcar como const las variables miembro que no cambian. Aclara el compromiso documentado entre la corrección de const y mover contenedores, incluida la opción del getter para el campo private descrita en el issue, y luego verifica el documento renderizado.

Escrito por el modelo de indexación a partir del texto del issue.