Prepare engineering teams to adopt Build Insights

## Business value

Clear communication will help engineering teams move confidently from Build Analysis to Build Insights and benefit from its improved build investigation and Known Issue experience.

## Expected outcome

After initial validation confirms Build Insights is ready for broader use, colleagues understand its value, know how to access it, start creating Known Issues through Build Insights, and have a clear way to get help or report problems.

## Acceptance criteria

- The launch communication explains the business impact of moving from limited validation to broader adoption.
- [Build Analysis](https://helix.dot.net/BuildAnalysis) displays a note linking to Build Insights and recommending it for supported workflows.
- Access instructions are published and linked from the communication.
- Colleagues are instructed to use the Build Insights **Create Known Issue** experience.
- An issue-reporting path, required diagnostic information, and responsible owner are agreed and documented.
- A Build Insights talk or demonstration is delivered, with reusable materials shared afterward.
- Communication links to the Build Insights guidance produced by [#6594](https://github.com/dotnet/arcade-services/issues/6594).

---
🤖 _Drafted by an AI agent on behalf of @michalpavelka._

Start with the Build Analysis entry point and the Build Insights guidance linked from #6594. Confirm that the launch communication, access and issue-reporting instructions, Known Issue workflow, Build Analysis link, and reusable talk materials are published and connected as specified.

Written by the indexing model from the issue text.