Users are now able to check whether a Data is visible from the
current context via `chisel.reflect.DataMirror.isVisible`.

* Bump versions
* It now tabs every line included in the Release Notes section of
  the PR template

Also fix website API doc link generation, links prior to 3.5.4 are not
valid (that is when we started publishing the unidoc properly so that it
gets picked up by javadoc.io and the like).

Co-authored-by: jackkoenig <jackkoenig@users.noreply.github.com>

Using `Output()` shouldn't drop important type information,
only override the specified direction to force alignment.

Until #3647 is addressed, use `cloneTypeFull` to get the expected behavior.
The cloned direction information is unnecessary but is
overridden by the coerced direction.

cc #3647.

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

The automation around automatically determining released versions of
Chisel and generating content for the website would fail in the period
between tagging a new release and the corresponding artifacts actually
being released to Maven Central. This would even prevent the CI job
trying to push the release to Maven Central.

Now, the logic for determining releases will filter for those actually
pushed to Maven Central.

* Make already deprecated APIs package private
* Add deprecation warnings to a few that we missed

* Bump SBT to latest (1.9.8)

* [CI] Change all ubuntu runners to ubuntu-22.04

This bumps some things running on the older runner which seems to have a
problem with SBT 1.9.8. It also removes any uses of ubuntu-latest to
ensure that we control the version explicitly.

* Width, KnownWidth, and Unknown width promoted to package chisel3
* Other classes moved to new package private chisel3.internal.firrtl.ir

Also change to an object (from a def) so that it shows up in ScalaDoc
search.

This avoids starting any Bloop servers which avoids hangs in CI.

* Revert "[binder] Remove firtool-1.61.0 features"
* [binder] Implement OM
* [binder] Implement probe IR emissions
* Change Trace API to only trace leaves (#3682)

Change the behavior of the Trace API to only trace leaves.  This aligns
with recent changes to CIRCT which error if annotations are applied to
aggregates which are then mandatorily split due to FIRRTL ABIs.  This
should have no practical effect on use of the Trace API only that
downstream consumers will need to work at the level of leaf types and not
on aggregates.

* [binder] Truncate for aggregate connection
* [binder] Set `inner_sym` only when needed
* [binder] Set module visibility
* [binder] Add function for exporting split verilog
* [binder] Support secret ports
* [binder] Refer with `SourceInfo` instead of `MlirLocation`
* [binder] Emit IR for probe read
* [binder] Handle secret ports for instance
* [binder] Fix extmodule emission
* [binder] Handle secret commands
* [binder] Handle probe ops without `Node`
* [binder] Flush the buffer at the end of `Writable` streams
* [binder] Keep original integer types from foreign API
* [binder] fix return type of asAsyncReset
* [cd] Bump CIRCT from firtool-1.61.0 to firtool-1.62.0

Signed-off-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
Co-authored-by: Schuyler Eldridge <schuyler.eldridge@sifive.com>
Co-authored-by: Sprite <SpriteOvO@gmail.com>
Co-authored-by: Jiuyang Liu <liu@jiuyang.me>
Co-authored-by: chiselbot <chiselbot@users.noreply.github.com>

Co-authored-by: Aditya Naik <aditya.naik@sifive.com>
Co-authored-by: Jack Koenig <koenig@sifive.com>

To override which firtool is used by Chisel, users should now set
environment variable CHISEL_FIRTOOL_PATH (rather than the old
FIRTOOL_PATH).

bump and update nix to use upstreamed packages

When creating large numbers of Definitions, copying the
globalNamespace back and forth becomes a performance bottleneck.

Now it will fetch llvm-firtool with classifier for the current system
rather than the full artifact which contains binaries for all platforms.

Legacy `--print-ir-after-all` has been replaced by this new argument.

* Use Java 17 to build documentation in CI

This avoids CI flakiness due to scala-cli needing to download Java 17 at
runtime and timing out.

* Exclude docs project from Unidoc

The docs project includes logic only used for generating mdoc, it should
not be included in the generated ScalaDoc as it is not actually included
in the published Chisel artifacts.

This also helps avoid flaky CI issues--the publish step will no longer
compile the docs subproject. Compiling the docs subproject requires
scala-cli which requires Java 17. Downloading Java 17 at build time can
timeout, causing flaky CI. Note that the publish step uses Java 8 so
that we can guarantee the published artifacts work on Java 8.

fix up path issue in build.sc

Whereas in the past, the user was expected to provide the firtool binary
on the PATH, Chisel will now manage the firtool binary automatically.
Chisel users the following 3-step process for determining which binary
to use:

1. If environment variable FIRTOOL_PATH is set, it will check for
   firtool in that directory
2. It will check the classpath for firtool provided by
   chipsalliance/llvm-firtool
3. It will download a default version of chipsalliance/llvm-firtool

Both (2) and (3) will store the firtool binary in a sensible location
depending on the user's operating system. See dirs-dev/directories-jvm
for more information. The user can override this location by setting the
FIRTOOL_CACHE environment variable.

* [docs] Fix release ordering
   Ensure that 6.0.0 > 6.0.0-RC1 > 6.0.0-M3
* [docs] Release candidates count for latest