Change FIRRTL emission to use FIRRTL 3.0.0 syntax for registers with a
reset.  The old emission was:

    reg a: UInt<1>, b with : (reset => (c, d))

The new emission is:

    regreset a: UInt<1>, b, c, d

Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>

Fix firrtl tests.

Update emitted FIRRTL version to 3.0.0.

Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>

Migrate all tests to new connect/invalidate syntax.

Change FIRRTL emission to use "connect a, b" and "invalidate c".  These
are newer styles that are much easier for FIRRTL compilers to parse as
they do not require lookahead.

Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>

This enables Chisel users to use these newer Scala versions.

Fix up code underlying `compile` used in many tests to
put annotations at the head of chirrtl
removed writing of WriteOutputAnnotations
removed passing in of json created by WriteOutputAnnotations files to firtool
Moved two tests in TraceSpec to use in instead of ignore

Fix a bug in BoringUtils (and secret IO APIs) where APIs would return a
Data.  This could create problems if the BoringUtils APIs were used
directly in operations, e.g., the following could cause a problem:

    val a = b & BoringUtils.bore(c)

This requires some casting of DontCare as it is unfortunately not a proper
"bottom" type.

No test is added as the test is that Scala passes type checking.

Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>

The updated versions fix warnings about deprecated actions.

Change FIRRTL emission to use a simpler syntax for registers without a
reset.  Previously, this used a self-reset with a zero reset signal.
Simplify this to emit a register without a reset.

Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>

Co-authored-by: Jack Koenig <koenig@sifive.com>

* Add Top-level parameterized reset type
* Add the ability to set the top reset type for any Module

Make the lines of code that need to be touched in the template fewer

This does not seem to be required by Scala, but it is required by newer
versions of SemanticDB (and thus to use Scala Metals).

* Update upickle to 3.1.0
* Update os-lib to 0.9.1

---------

Co-authored-by: Jack Koenig <koenig@sifive.com>