Bumps com.gradle.enterprise from 3.12.4 to 3.12.5.

---
updated-dependencies:
- dependency-name: com.gradle.enterprise
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Checks if the registry is closed before calling publish on close. This avoids side effects of calling close multiple times.

Resolves gh-3712

Bumps com.gradle.enterprise from 3.12.5 to 3.12.6.

---
updated-dependencies:
- dependency-name: com.gradle.enterprise
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

We do not need to be on snapshots now, and unfortunately this made it out in a release.

Resolves gh-3738

There is better memory and CPU performance with plain old iteration.

Without this change, there were still consistency issues detected despite the synchronization.

Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>

The Scope#makeCurrent method is called e.g. via ObservationThreadLocalAccessor#restore(Observation). In that case, we're calling ObservationThreadLocalAccessor#reset() first, and we're closing all the scopes, HOWEVER those are called on the Observation scope that was present there in thread local at the time of calling the method, NOT on the scope that we want to make current (that one can contain some leftovers from previous scope openings like creation of e.g. Brave scope in the TracingContext that is there inside the Observation's Context.

When we want to go back to the enclosing scope and want to make that scope current we need to be sure that there are no remaining scoped objects inside Observation's context. This is why BEFORE rebuilding the scope structure we need to notify the handlers to clear them first (again this is a separate scope to the one that was cleared by the reset method) via calling ObservationHandler#onScopeReset(Context).

When we reset a scope, we don't want to close it thus we don't want to remove any enclosing scopes.

With this logic we reset any existing scopes on reset by calling the handler + when we make an enclosing scope current we will remove it from the list of enclosing scopes.

Closes gh-3752

 Closes gh-3753

 Closes gh-3754

 Closes gh-3755

 Closes gh-3756

 Closes gh-3757