[wiki migration] Android team pages (#148585)

This puts the wiki pages owned by the Android team into the docs/platforms/android directory as planned in [flutter.dev/go/migrate-flutter-wiki-spreadsheet](https://docs.google.com/spreadsheets/d/1x65189ZBdNiLRygpUYoU08pwvXD4M-Z157c6pm8deGI/edit?usp=sharing) 

It also adds the android team labels to the label bot for future PRs.

Changes to the content were only updating cross links, or link to refer to the main branch rather than master.
Remaining links to the wiki will be updated once all other pages have finished moving, they still work in the meantime.

Part of https://github.com/flutter/flutter/issues/145009

.github/labeler.yml

@@ -48,6 +48,11 @@
     - any-glob-to-any-file:
       - examples/api/**/*
 
+'d: docs/':
+  - changed-files:
+    - any-glob-to-any-file:
+      - docs/**/*
+
 'd: examples':
   - changed-files:
     - any-glob-to-any-file:
@@ -126,6 +131,11 @@ package:
     - any-glob-to-any-file:
       - docs/ecosystem/**/*
 
+platform-android:
+  - changed-files:
+    - any-glob-to-any-file:
+      - docs/platform/android/**/*
+
 platform-ios:
   - changed-files:
     - any-glob-to-any-file:
@@ -148,6 +158,11 @@ platform-web:
       - '**/*.expect'
       - '**/*test_fixes*'
 
+team-android:
+  - changed-files:
+    - any-glob-to-any-file:
+      - docs/platform/android/**/*
+
 team-ecosystem:
   - changed-files:
     - any-glob-to-any-file:

docs/platforms/android/Android-Platform-Views.md

@@ -29,9 +29,9 @@ within their Flutter UI.
 # Approaches
 
 There are currently three different implementations of Android platform views:
-- [[Virtual Display]] (VD)
-- [[Hybrid Composition]] (HC)
-- [[Texture Layer Hybrid Composition]] (TLHC)
+- [Virtual Display](Virtual_Display.md) (VD)
+- [Hybrid Composition](https://github.com/flutter/flutter/wiki/Hybrid-Composition) (HC)
+- [Texture Layer Hybrid Composition](Texture-Layer-Hybrid-Composition.md) (TLHC)
 
 Each has a different set of limitations and tradeoffs, as discussed below. The pages linked above give details about each implementation.
 
@@ -39,7 +39,7 @@ Each has a different set of limitations and tradeoffs, as discussed below. The p
 
 This mode works by rendering the platform view into [a `VirtualDisplay`](https://developer.android.com/reference/android/hardware/display/VirtualDisplay), whose contents are connected to [a Flutter `Texture`](https://api.flutter.dev/flutter/widgets/Texture-class.html).
 
-Because this renders to a `Texture`, it integrates well into the Flutter drawing system. However, the use of `VirtualDisplay` introduces a number of compatibility issues, including with text input, accessibility, and secondary views (see [[the Virtual Display page|Virtual Display]] for details).
+Because this renders to a `Texture`, it integrates well into the Flutter drawing system. However, the use of `VirtualDisplay` introduces a number of compatibility issues, including with text input, accessibility, and secondary views (see [the Virtual Display page](Virtual-Display.md) for details).
 
 This display mode requires SDK 20 or later.
 

docs/platforms/android/Texture-Layer-Hybrid-Composition.md

@@ -1,8 +1,8 @@
-_See also: [[Hybrid Composition|Hybrid Composition#Android]]_
+_See also: [Hybrid Composition|Hybrid Composition#Android](https://github.com/flutter/flutter/wiki/Hybrid-Composition)_
 
 # Background
 
-Texture Layer Hybrid Composition (TLHC) is one of several modes for displaying platform views on Android. See [Android Platform Views](https://github.com/flutter/flutter/wiki/Android-Platform-Views) for an overview of modes.
+Texture Layer Hybrid Composition (TLHC) is one of several modes for displaying platform views on Android. See [Android Platform Views](Android-Platform-Views.md) for an overview of modes.
 
 It was introduced in Flutter 3.0 to combine the best aspects of Virtual Display and Hybrid Composition while addressing their most significant issues. While it was originally intended to replace both, it turned out to have some limitations that prevented serving as a complete replacement, so is now a third option.
 

docs/platforms/android/Upgrading-pre-1.12-Android-projects.md

@@ -2,7 +2,7 @@ _If you `flutter create`d your project prior to version 1.12, this may apply to
 
 # Background
 
-In order to better support the execution environments of adding Flutter to an existing project, the old Android platform-side wrappers hosting the Flutter runtime at [`io.flutter.app.FlutterActivity`](https://github.com/flutter/engine/blob/master/shell/platform/android/io/flutter/app/FlutterActivity.java) and their associated classes are now deprecated. New wrappers at [`io.flutter.embedding.android.FlutterActivity`](https://github.com/flutter/engine/blob/master/shell/platform/android/io/flutter/embedding/android/FlutterActivity.java) and associated classes now replace them.
+In order to better support the execution environments of adding Flutter to an existing project, the old Android platform-side wrappers hosting the Flutter runtime at [`io.flutter.app.FlutterActivity`](https://github.com/flutter/engine/blob/main/shell/platform/android/io/flutter/app/FlutterActivity.java) and their associated classes are now deprecated. New wrappers at [`io.flutter.embedding.android.FlutterActivity`](https://github.com/flutter/engine/blob/main/shell/platform/android/io/flutter/embedding/android/FlutterActivity.java) and associated classes now replace them.
 
 Those classes better support real world scenarios where the FlutterActivity isn't the first and only Android Activity in an application.
 

docs/platforms/android/Virtual-Display.md

@@ -1,6 +1,6 @@
 # Background
 
-Virtual Display is one of several modes for displaying platform views on Android. See [[Android Platform Views]] for an overview of modes.
+Virtual Display is one of several modes for displaying platform views on Android. See [Android Platform Views](Android-Platform-Views.md) for an overview of modes.
 
 # The approach