Consider removing the 'Field list' reports

-1 to removing it, seems like a useful overview of a site, especially ones you didn’t build yourself.

Maybe it should move to Structure somewhere?

I think this was more useful when fields could be re-used across entity types, now they're per-entity type, so it's much more straightforward to check this information in the actual field UI - at least with a low-ish number of bundles.

@dww have you ever used this report?

To me this could live in https://www.drupal.org/project/site_audit →

I have used it a handful of times to try to get a handle on a site’s content model, probably in mapping out a migration or rebuild. If you aren’t familiar with the site and it has a lot of paragraph types for example, it can give you an idea what is being used where. That’s especially true if there are nested paragraphs.

There are probably better ways to do it though, and I can’t say I would be particularly bothered if it were removed.

I personally use this report a lot especially to understand the architecture of websites I did not build myself, or just to remember how I handle data in websites built years earlier.

Personally I think the only way to avoid such a report would be to get rid of sharing fields acros entity bundles entirely (which would in turn simplify field UI and maybe the internal Entity field API). Just my 2 cents