[APIView] Epic: Cross-Language Features

A requirement for the archboard revamp process to enable automated reviews and approvals is a way to have a cross-language conversation in APIView.

**This issue is not to track implementation, but to track the need to develop and vet a solution, as this is still very ill-defined.**

We have discussed a couple ways this might manifest, based on the work that has already been done in APIView to enable cross-language IDs.

**Cross-Langauge Conversations Tab**

This would present a unified conversations tab that would include comments (and context snippets) for comments across all languages for a given review, allowing any architect to see the conversations for every other review. In this view, comments could be marked as applicable to one or more languages to identify and resolve cross-language impacts.

This view would allow replies to existing comments, but would not allow the creation of new comments (just like the current conversations tab today)

**Cross-language Review Page**

This would present some common form--likely TypeSpec--where architects could leave feedback and mark that feedback as relevant to one or more languages. This view would show only syntax that has a cross-language ID, and architects would be able to easily see how that concept is rendered in their language.

**Dashboard**

There is some sketch of a cross-language dashboard that would show the "10,000 ft view" for all languages for a given package.