Remove configurability of 'isFatal' (#10212)

* Remove configurability of 'isFatal'

* Introduce `zio.NonFatal`

* Replace usage of scala.util.control.NonFatal

* Move nonFatal method to zio package

Deprecate adding Fatal to the Runtime (#10200)

This is a followup, as I missed it in #10140

[test-sbt] More uniformity. (#10120)

* [test-sbt] More uniformity.

Currently, code implementing `sbt.testing.Framework` for JVM, Scala.js and Scala Native suffers from severe code triplication: code doing the same thing is present in three places. This pull request removes this gratuitous redundancy.

An unfortunate - and inevitable - consequence of code duplication is code drift: different copies of the code do things differently for no good reason.

Backends `sbt.testing.Framework` runs on _do_ have inherent differences: tests running on Scala.js and Scala Native are not running on JVM, and thus their outcomes need to be communicated to the process managing the test run; Scala.js is single-threaded by nature, which affects the way tests have to be run.
Code differences not warranted by the inherent differences between the backends seem gratuitous, and this pull request removes some of them.

One area where implementations of the `sbt.testing.Framework` diverged from one another is the machinery to test them: only JVM implementation is currently testable. With this pull request, `sbt.testing.Framework` tests run on all the backends.

Another divergence is in the storage of test summaries: JVM uses `AtomicReference[Vector]`, Scala.js uses `Buffer`, Scala Native uses `ConcurrentLinkedQueue`; this pull request unifies summary storage for all backends: `AtomicReference[Vector]` works for all of them.

Another divergence is the way test summary is rendered: counts of tests executed, ignored, or failed are included in the summary on JVM but not on Scala.js or Scala Native; setting test renderer to IntelliJ in the test arguments is honored only on JVM. This pull request makes test summary uniform across the backends.

Another divergence is: currently, signal handlers are installed only on JVM. This pull request installs them on all backends.

Another divergence affects a recent [enhancement](#9756), which turned out to be effective only on JVM; this pull request applies it to all backends (and tests that it works ;)).

@kyri-petrou, your [remark](#9629 (comment))

> I gave it a go at this (basically trying to unify the JVM / JS / Native implementations so that we can reuse the existing event test suites that exist for the JVM, but it doesn't seem possible.
> ... writing a full test suite from scratch (which frankly it's going to be extremely time consuming)

is on target: this was not trivial ;)

* [test-sbt] More uniformity.

Address review comments.

* [test-sbt] More uniformity.

Address more review comments.

* [test-sbt] More uniformity.

Address more review comments.

Fix release CI (#10038)

* Fix release CI

* Set fetch-depth to 0

Fix awaiting application finalizers to run on external interruption (#…

…9908)

* Fix issue with application not awaiting finalizers to run on exit

* Add comment

* Remove trySet

* Handle negative timeouts

* Remove unused import

* Update ZIOAppPlatformSpecific.scala

Co-authored-by: Adam Hearn <[email protected]>

---------

Co-authored-by: Adam Hearn <[email protected]>

Ignore failing Cause test (#9863)

Make metrics names compatible with Prometheus Java library (#9740)

Update magnolia to 1.3.15 (#9645)

Co-authored-by: zio-scala-steward[bot] <145262613+zio-scala-steward[bot]@users.noreply.github.com>

Update magnolia to 1.3.10 (#9549)

Co-authored-by: zio-scala-steward[bot] <145262613+zio-scala-steward[bot]@users.noreply.github.com>

More efficient parsing of line numbers without string allocations (#9433

)

* More efficient parsing of line numbers without string allocations

* Avoid double scanning of the line number part of the trace string + add missing unit tests

* Fix formatting