Eliminate NonCopyable approach

[even1024]

NonCopyable class should be removed from Indigo. All the derived classes should have proper deep copy constructors and move constructors.

[AlexanderSavelyev]

non-copyable was created for a performance reason. The task should not be done without performance impact evaluation for the Indigo calculations. Have proper deep copy constructors - for all classes assumes that someone can have copy objects where it is not necessary. Alternative possible option is to have move constructors defined, but not copy. Deprioritizing the task until providing more details