…metry into feature/netcore

Gives context to logs downstream in GE when using structured logging

…metry into feature/netcore

…metry into feature/netcore

…ape service method

…metry into feature/netcore

…metry into feature/netcore

…metry into feature/netcore

…metry into feature/netcore

…metry into feature/netcore

…ctors arg

…metry into feature/netcore

…metry into feature/netcore

…metry into feature/netcore

* Refactored Dependency injection approach.
Previously was convoluted and relied on side effects in a custom assembly resolver; meaning consumers could not use the engine at all unless invoking the ServiceCollection.AddXbimGeometry extension method.

XbimGeometryengine is now Injectable - but requires a model to be explicitly registered before invoking Geometry

* Added more DI friendly means of configuring Geometry engine

Using a Builder pattern to define injected Configuration

* Handle edge case in invalid models where a single context is provided but items are not linked to it.

* Fixed up GE interfaces so Managed engine exposes Register abilities.
Ensured that same instance of GE supplied in scope regardless of interface used

* Added guard so clearer what happened if caller used DI and did not Register a model. Gives useful exception rather than NRE

* Added simpler interface to creating Geometry Engine using a Factory Managed engine exposes options

* Added some nullchecks and fallbacks for null logging inputs

…ns under another folder (e.g. Azure functions.exe)

…ommon

Removed recently introduced Geometry DI services

i.e. Logging is optional
Also use 6.0.0 versions over 3.1.1

…verlapping geometry are discarded

Service registrations made idempotent
Added Geometry Registration to the XbimConfigurationBuilder
Added sanity checking in cases services are not available

Trimmed public surface areas slightly

Reinstate tests in Devops

… trait to allow CI filtering

Rationale: So we get a clean build through and can track fixes and further regressions.
Expected 16 skipped tests (actually 18 due to skipped Theorys)

TODO: SolidFactory.Build(IfcHalfSpaceSolid) implementation
Fixed Build Warning in XbimSolidSet

…ondeterministic ordering or tests

Rationale: don't overload the logs (e.g. Seq) with lots of Information logs at volume
Information = all is well at a high level in the process. Started / Finished a job etc
Warning = you probably want to fix this (but... don't want to overload the user, or us, with them)
Debug = to help with diagnostics when things are not as expected. we fixed and issue and carried on
Error = Something broke irreparably- the end result is probably not what was hoped for

…tion rather than the wrapper.

Add context to the logger scope so output is the same. This preserves stack traces etc at the top level.
The wrapper exception will typically get logged higher in the stack anyway.

Sensitive to environmental factors and other machine activities

Rerun failed tests up to 3 times  - for occasional transient issues