Support for RSM plots

[ka-sarthak]

TODO

• [x] Data coming from the readers is a dict: for each key, there is a list of pint.Quantity. Each element of this list corresponds to one line scan. For RSM we have len(list) = n, for 1D line scan, we have len(list) = 1
• [x] Extend the vector quantities related to intensity and positions to accept matrix.
• [x] Handle the normalizing (plots, q-vectors) for both 1D and 2D data under the same schema
  • [x] Add calculation of q-vectors for 2D
  • [x] Add plotting for RSM (interpolation needed for Q-space rsm)
• [x] Improve the plots and visualization ~(also explore datashaders for high resolution scans)~
• [x] Harmonize the changes for brml, xrdml, rasx files
• [x] Add interfacing functions that evaluates the type of scan based on data received from readers. detect_scan_type, modify_scan_data
• [x] A separate class for RSM and 1D line scan which extends a common XRDResult schema.
• [x] Add tests for new util functions and readers
• ~RSM plot that does not bottlenecks the network~ (to be fixed later, for now, reduced the data load by squeezing data vectors wherever information is repeated)
• ~Use long arrays to represent the 2D data. This allows the datatype for axis and intensity to be the same as in 1D.~
• ~Data coming from the readers should be full matrix. Remove selection of first line scan in case of 2D data~

[ka-sarthak]

A hacky fix for Brucker reader which was needed to process both 1d and rsm scans.

RawData field in rawfile containing the measurements has different data structure for 1d and 2d scan. For 1d, it is a list of dict, where length of the list is the number of measurements. While for 2d, in each of the rawfile, it is a list of values.

The axis position has to be calculated using start, end, step-size of the axis. But this can sometimes lead to 1 extra value for the position than the number of measurement values leading to a mismatch in dimensions for intensity and axis. Resolved this by using number of MeasurementPoints (available in the raw file) directly to calculate axis position array (which happens to be the case for 1d scan testfiles). In case, MeasurementPoints is equal to 1 (which appears to be the case for RSM test files), use step-size of the axis instead along with it's start and end position to determine the array of axis positions.