Add an integrated Environment Insights and Observability section to IBM DevOps Deploy

NOTE:  We have a model of this now we have been testing.  We take the diagnostic bundle then generated an HTML page with all the relevant information.. I'll attach a a document that shows what we are looking to accomplish and benchmark. 

Summary:
Introduce a native section in DOD that brings together environment inventory, ownership, platform health, governance, and deployment trends in one actionable dashboard. The goal is to help administrators and service owners answer three questions without manually assembling exports and diagnostic logs: What do we have? Is it healthy? What needs attention?

Business problem:
Enterprise deployment platforms accumulate applications, components, teams, integrations, and infrastructure over many years. Understanding the overall estate requires more than viewing individual objects or deployment results. Today, obtaining a consolidated view requires manual exports and log analysis, produces point-in-time information, and relies on custom interpretation of relationships, configuration settings, and log events. A native capability would be more consistent and more useful to administrators, application owners, auditors, and leadership.

Proposed capability
An Environment Insights section with the following views:

• Executive overview: Estate size, ownership distribution, key health indicators, emerging risks, and prioritized actions.
• Footprint explorer: Interactive navigation across owners, applications, components, environments, and their relationships.
• Searchable directory: Filterable inventory with ownership, descriptions, tags, integration status, and links to the underlying DOD objects.
• Governance and hygiene: Documentation coverage, effective retention policies, ownership gaps, and candidates for review (not automatic declarations that objects are unused).
• Platform health: Node-level error trends, recurring error categories, request performance, cleanup activity, and relevant configuration observations.
• Deployment and infrastructure health: Current and recent deployments, failure patterns, agent and relay connectivity, and supported capacity indicators.
• Action plan: Evidence-backed recommendations with severity, affected objects, suggested next steps, and drill-down links.

Every view should show its data source, observation time, reporting window, and completeness. Missing or stale observations must be distinguishable from healthy results or zero activity.