Inconsistency between ITKImageProcessing vector images and DREAM3D vector images

ITKImageProcessing encodes RGB(A) and vector images in Dream3D data container differently whereas DREAM3D encodes them the same way.

In DREAM3D,
RGB(A) and vector images: QVector cDims(1, nb_components);

In ITKImageProcessing:
Vector images components: QVector cDims(nb_components, 1);
RGB images: QVector cDims(1, 3);

ITKImageProcessing uses this implementation difference to differentiate between RGB(A) images and vector images. A solution for ITKImageProcessing to differentiate between RGB(A) and vector images could be with additional input from the user (check box). This additional input would be selected at the filter level.

Start by comparing the ITKImageProcessing and DREAM3D representations in the issue: RGB(A) and vector image component dimensions are encoded differently. Clarify whether the intended fix is consistent encoding or a filter-level user checkbox, then verify that RGB(A) and vector images remain distinguishable in the Dream3D data container.

Written by the indexing model from the issue text.