Change member functions and data names in vector and matrix classes to be more consistent

[pelesh]

Change names of methods and data members in vector and matrix classes to be more consistent and accurate. Specific changes include:

• Matrix classes (Sparse, Csr, Csc, Coo)
  • Rename setMatrixData to setDataPointers
  • Rename setNewValues to setValuesPointers
  • Rename updateData to copyData
  • Change input data arrays in copyData to const arrays.
  • Rename owns_*_data_ to owns_*_sparsity_pattern_
• Vector class
  • Rename deepCopyVectorData to copyDataTo
  • Rename update to copyDataFrom.

Fixes #167

[pelesh]

Rebased to develop.

[shakedregev]

Tests are passing, looks good besides the minor comments

[nkoukpaizan]

I haven't looked at codes changes, but tests are passing for me as well (tested on Frontier).

[kswirydo]

My main concern is that now we have copyData[To/From] instead of update but at the same time, we kept setDataUpdated which makes things slightly more confusing.

[pelesh]

My main concern is that now we have copyData[To/From] instead of update but at the same time, we kept setDataUpdated which makes things slightly more confusing.

I am not sure if this makes things more confusing. The purpose of setDataUpdated is to tell matrix/vector object that its data was changed externally by accessing its raw data pointers. The setDataUpdated is not used in conjunction with copyData* functions because the latter set internal matrix/vector flags to indicate if any object data was changed (updated) during the copy. Perhaps a better name would be setDataChanged?