Ncrystal

* RC1 for incoming release v3.6.0.

* Redo VDOS integrals for gamma0 and Teff to support much lower
temperatures (down to 0.001K certainly no issue now).
* Ensure that the evaluation of the G1 function is now numerically safe,
even at very low temperatures where the detailed balance factor becomes
numerically indistinguishable from 0 or infinity (github issue 109).
* Trim excess zeroes at edges of G1 function.
* Unify temperature range checks. More specifically, replace asserts which
were imposing temperature limits inconsistent with those allowed by the
"temp" cfg-parameter (1e-3K to 1e6K).
* Make FileListEntry returned by NCrystal.browseFiles sortable.
* Fix ncrystal_endf2ncmat (github issue 110).

* Migrate names of all CMake parameter options to be prefixed with
"NCRYSTAL_". Using the old names will mostly keep working for the time
being, but will cause a warning to be issued (mctools/ncrystal105).
* No longer build and install examples by default.
* We now newer fiddle with CMAKE_BUILD_TYPE if a multi-cfg generator is
detected.
* Add option NCRYSTAL_ENABLE_CPACK. If set, a few CPACK-related variables
will be set and an "include(CPack)" statement is triggered just after
the "project(..)" statement (mctools/ncrystal107).
* Rename CMake target "common" to "ncrystal_common" to avoid clashes when
project is build as a subproject (mctools/ncrystal105).
* Completely ignore the CMake option BUILD_EXTRA which has not been
supported since release v3.0.0.
* Minor fix for setup.py file generated from CMake, needed to work with some
outdated python installations.
* Add hidden --pytrace option to ncrystal_inspectfile and nctool, for
running the script under the python trace module.
* A few fixes for Windows (thanks to Peter Willendrup). In particular,
never use aligned_alloc on windows.

* Expose utility for completely flattening a material composition to
Python interface, as a new info.getFlattenedComposition() method. This
is intended to better support materials with non-natural compositions in
the OpenMC bindings. Internally, the new method is using the same
machinery as what is already in place to provide the same functionality
for the Geant4 bindings.
* ncrystal_onlinedb2ncmat was not using new unified cmdline script
machinery introduced in v3.4.0, which has now been corrected.

* Modify location of CMake config files provided by an NCrystal
installation, to hopefully make it easier for downstream projects to
locate an existing NCrystal installation (more details on this MCPL
issue: https://github.com/mctools/mcpl/issues/58).
* Modify manner in which Geant4 bindings must be activated in downstream
CMake code. Previously they were enabled via a dedicated
"find_package(G4NCrystal)" call, but now they are instead provided as an
optional COMPONENT when requesting the NCrystal package:
"find_package(NCrystal COMPONENTS GEANT4BINDINGS )" and if succesful the
downstream binaries must be configured to depend on the G4NCrystal
interface by adding the NCrystal::G4NCrystal target as a dependency,
i.e. "target_link_libraries( mybinary NCrystal::G4NCrystal )". The
Geant4 bindings will not be enabled unless the GEANT4BINDINGS component
is explicitly requested.
* Unify manner in which shipped cmdline scripts look for NCrystal python
module.

* Fix info.getComposition() for multiphase materials in the Python
interface. This issue is not believed to have affected many users, but
a fix is crucial in order to support multiphase materials in OpenMC
hooks which are currently being prepared (github issue 102).
* Minor fix to make Geant4 hooks work with Geant4 release 11. Note that
this is still not the long awaited major update which makes the hooks
work with Geant4 in multithreaded mode.
* Rewrote internal code in NCIter.hh to avoid usage of deprecated
std::iterator. This avoids compilation warnings on newer platforms
(github issue 100).
* Reduce precision from %.15g to %.14g in output of ncrystal_ncmat2hkl to
get reproducible results across platforms.