Const correctness of PackedImageDesc

In our use case, we are passing const void pointers to build a source `PackedImageDesc` for use in `CPUProcessor::apply`. However, `PackedImageDesc` requires a non-const pointer. I assume this is so that users with non-const data can call `getData` and modify the result. This makes it dangerous to const_cast our pointer as a caller could then end up inadvertently modifying a const buffer through those calls.

Perhaps there should be a `ConstPackedImageDesc`? Or is the design to keep the scope of `PackedImageDesc` tightly around the `apply` call so that it's unlikely that users can access the `getData` functions?

Comienza siguiendo PackedImageDesc a través de CPUProcessor::apply y revisando las funciones getData mencionadas en el issue. Determina el comportamiento previsto de const-correctness y si es apropiado un ConstPackedImageDesc separado o un alcance más restringido limitado a apply; se considera terminado cuando la dirección de la API está acordada y especificada.

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