[dv] reports.opentitan.org RTL coverage results are stale since Feb 2025

Nobody has claimed this yet.

### Description

Hi all, I am new to this project. I'm interested in understanding and replicating the DV flow.
On OpenTitan's [dashboard](https://opentitan.org/dashboard/index.html) tab, the DV dashboard links to [nightly OpenTitan Regression tests](https://reports.opentitan.org/hw/top_earlgrey/dv/summary/latest/report.html), which are timestamped:

> Saturday February 08 2025 05:05:54 UTC
> GitHub Revision: [9f20940d49](https://github.com/lowrisc/opentitan/tree/9f20940d494a223cc950a5b98f748fb28109d458)

Is the RTL coverage reporting pipeline still actively maintained? I ask since naively pulling master and running coverage on the UART block alone `util/dvsim/dvsim.py hw/ip/uart/dv/uart_sim_cfg.hjson -i nightly --cov` results in more test failures than I see online. My generated nightly summary report (UART only) is attached and hosted [here](https://people.eecs.berkeley.edu/~alecfv/assets/report-opentitan-master.html) for convenience.

[report.html](https://github.com/user-attachments/files/26325753/report.html)

Thank you for the help!

Start with the dashboard links and the latest report timestamp, then run util/dvsim/dvsim.py hw/ip/uart/dv/uart_sim_cfg.hjson -i nightly --cov as described. Compare the generated UART-only report with the linked nightly report and identify whether the reporting pipeline or test expectations account for the stale results. Done means documenting the pipeline status and explaining the discrepancy.

Written by the indexing model from the issue text.