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>

- Enable .viewAsSupertype to work on Records
- fix a nondeterminism error in DataView noticeable on error reporting

Enable a user to define Scala-time properties on an Interface.  These
properties require a conformance to examine.  This enables patterns where
a client wants to configure itself based on knowledge of the component,
e.g., when the client is a testbench.

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

Make the frequency a legal value (14 days).

Fix a bug in naming where a Module that took a Unit parameter could cause
naming to crash.  This is, admittedly, a very weird pattern, but can occur
if you have a type-parametric module where certain type parameterizations
can be Unit.

Fix #3245.

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

Fix a bug in the new BoringUtils.bore API where this would generate
invalid FIRRTL if the user did boring which created a path that went up to
an LCA and then down.  Change the internal leastCommonAncestor utility to
also return the LCA module as this avoids a second call to compute the
LCA.

Fixes #3239.

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

Change what DataView allows in its type checking to enable Reset to be
viewed as either a UInt<1> or an AsyncReset.  This enables more flexible
DataViews which match already allowable Chisel and FIRRTL connection
semantics.

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

The Mergify-generated backports do not currently include the information
needed by the release notes generation automation. This new workflow
will copy such information over to backport PRs.

* Mark generated wires for read and readWrite as temporary
* Remove semicolons
* Remove intermediate wire for read/readWrite port address
* Convert usages of UnlocatableSourceInfo into macro applications

* Add .unsafe to connectables

* Added .as and .squeezeAllAs to connectable

* Make connectable exceptions error at end of elaboration

Bump firtool version to get parsing of new connect/invalidate
statements.

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

Fix a bug where the name of the Stub module (a module auto-generated from
an Interface without an implementation available) would be called "Stub"
as opposed to the name of the Interface.  This could create a linker error
if the Stub was used.

Fix this setting the final "desiredName" inside the Entity.  Add a test that
this works for the Stub.

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