fix(docs-site): render <Language> blocks that list multiple languages

`Language` typed its prop as a single language and tested the path with
`pathname.includes(`/${language}/`)`. Four call sites pass an array, which
stringifies to "typescript,python", so the test looked for the path segment
`/typescript,python/`, never matched, and the component returned null —
silently dropping its children on every page.

Accept `Language | readonly Language[]` and match if any listed language
matches the current path.

This restores content that was invisible sitewide, not just on the auth
page: the two intro paragraphs on the Essentials landing page and the
OAuth connection-name note both render again. Single-language gating is
unchanged.

Also add blank lines around the admonition inside that `<Language>` block
so the markdown is parsed, matching the surrounding convention.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Author: 2 people

teams.md/src/components/Language.tsx

@@ -3,15 +3,17 @@ import { useLocation } from '@docusaurus/router';
 import { type Language } from '../constants/languages';
 
 export type LanguageProps = {
-  readonly language: Language;
+  readonly language: Language | readonly Language[];
 };
 
 // Component for inserting language-specific content onto a page.
 export default function Language({ language, children }: PropsWithChildren<LanguageProps>) {
   const location = useLocation();
 
-  // Only render if current path matches language
-  if (!location.pathname.includes(`/${language}/`)) {
+  const languages = Array.isArray(language) ? language : [language as Language];
+
+  // Only render if current path matches one of the languages
+  if (!languages.some((lang) => location.pathname.includes(`/${lang}/`))) {
     return null;
   }
 

teams.md/src/pages/templates/in-depth-guides/user-authentication.mdx

@@ -48,9 +48,11 @@ Make sure you use the same name you used when creating the OAuth connection in t
 :::
 
 <Language language={['typescript', 'python']}>
+
 :::note
 In many templates, `graph` is the default name of the OAuth connection, but you can register the connection under any name — it just has to match the OAuth connection configured on the Azure Bot.
 :::
+
 </Language>
 
 ## Signing In