Thread-safety patches

See merge request !109

Consistently with how it has been implemented in GeoPhysVol

Also switched GeoPhysVol from std::lock_guard to std::scoped_lock

Option for using detector regions in FullSimLight with the appropriate set of volumes and production cut values.

See merge request !108

Avoid using region and logical volume store maps since they are available only in very recent Geant4 version.

A detector region configurator has been added with region settings (e.g.
name, secondary production threshold, list of root logical volume names)
that are the same (or very close to) that is used on production. These
configurations were generated by using the G4PhysicsRegionConfigNew.py
and G4GeomtryToolConfig.py scripts from Athena. Addig detector regions
can now be activated by the /mydet/addRegions UI command. A given region
is added only if at least one of the corresponding root logical volume
can be found in the geometry while it's simply skipped otherwise without
any problem.

General cleanup of the FullSimLight Geant4 application

See merge request !107

A significant clean up has been done on the application, especially
regarding the user actions. These were still identical to that I
developed for the GeantV project in the fullCMS Geant4 application
(that fullSimLight is based on). While the goal of that application
was to demonstrate even some more advanced user action features,
these are completely unnecessary for fullSimLight and causing only
limitations. So the user actions has been reduced, made simpler and
cleaner. Only a minimum set of infomation is collected now (only if
executed in non-performance mode) such as the mean energy deposit,
mean number of charged/neutral steps, mean number of secondary electron,
gamma and positron per event.

An additional option, for collecting the above infomation only
restricted to a given detector region, will be added later when
activating detector regions will already be implemented.

Note, that the same user actions can now be used both with the
particle gun and the Pythia primary event generator options.

Originally, a fixed (1234) seeding was used for seeding the RNG
of Pythia. In case of using Geant4 MT with multiple worker threads,
this results in generating exactly the same set of events for each
of the threads. This behaviour is kept now only for performance
mode runs (-p) while the worker thread generators are seeded now
using the event ID ortherwise. This results in a reproducible
set of events for the complete run while the individual worker thraeds
simulate distinct subsets of this.

Ported several code changes from the Athena version of GeoModelXml

See merge request !104

Porting Scott's changes from Athena (MR!47594)

Bug fix in GmxUtil::evaluate()

See merge request !103

Fixed wrong declaration of the thread_local variable

set a default value to ProcessorList in Gmx2Geo so that client code will not...

See merge request !102

set a default value to ProcessorList in Gmx2Geo so that client code will not in the least affected. Merging this branch after this correction

Synch-ed GeoModelXml with the latest updates in the Athena repository

See merge request !101

See the [merge request](atlas/athena!47262)
by Scott for more details

Rolled back two commits which affected Pow::operator()

See merge request !100

These commits are: 810d7a0f and e0e82eb7. The reason for the rollback is that
we want to understand why they lead to some changes in ATLAS G4 Sim outputs.

ExpressionEvaluator: Fix compilation warnings.

See merge request !99

GeoModelDBManager: Fix compilation warnings.

See merge request !98

GeoModelRead: Fix compilation warning.

See merge request !97

GeoModelRead: Fix placement of using directive.

See merge request !96

GeoModelKernel: Fix compilation warnings.

See merge request !94

GeoModelKernel: Fix race in RCBase::unref().

See merge request !95

Don't rely on falling through between switch cases.
Unused function parameters.

Uninitialized local variables.
Unused variable.

Unused variable.

    
Don't put a using directive in the global namespace in headers.

The decrement and test must be done atomically; otherwise we could have
a race.  E.g., suppose a RCBase object has a refcount of 2, and two threads
call unref simultaneously.  The two decrements could both happen before
either of the comparisons, resulting in a double-delete.

Order of member initialization.
Unused class data members.
Unused function parameter.