Update flavors guide for Android. (#11758)

_Description of what this PR is changing or adding, and why:_

This is a refactor of the Android Flavors guide that addresses several
developer requests, including steps to customize the app name and app
icons.

_Issues fixed by this PR (if any):_

Fixes: #11591 #11060 #10713 #10309 #10164 #9976 #9360 #9359 #9309 #8743
#8746 #8238

_PRs or commits this PR depends on (if any):_

This is part of a larger cleanup effort for the flavors documentation.
The first part of this cleanup addressed our iOS and macOS docs for
flavors. This was the final part of the cleanup.

## Presubmit checklist

- [x] This PR is marked as draft with an explanation if not meant to
land until a future stable release.
- [x] This PR doesn’t contain automatically generated corrections
(Grammarly or similar).
- [x] This PR follows the [Google Developer Documentation Style
Guidelines](https://developers.google.com/style) — for example, it
doesn’t use _i.e._ or _e.g._, and it avoids _I_ and _we_ (first person).
- [x] This PR uses [semantic line
breaks](https://github.com/dart-lang/site-shared/blob/main/doc/writing-for-dart-and-flutter-websites.md#semantic-line-breaks)
of 80 characters or fewer.

Author: antfitch

src/content/assets/images/docs/flavors/flavors-android-app-names-1.png

@@ -43,8 +43,6 @@ To learn more, check out [dart.dev/go/macros][].
 * We have three new codelabs and a new guide for the Games Toolkit.
   To see the list of additions,
   check out the updated [Casual Games Toolkit][] page.
-* A new section, [Conditionally bundling assets based on flavor][],
-  in the Flavors page.
 * Flutter support for Web Assembly (Wasm) has now reached stable.
   To learn more, check out the updated
   [Support for WebAssembly (Wasm)][] page.
@@ -70,7 +68,6 @@ To learn more, check out [dart.dev/go/macros][].
 
 [Adaptive and Responsive design]: /ui/adaptive-responsive
 [Casual Games Toolkit]: /resources/games-toolkit
-[Conditionally bundling assets based on flavor]: /deployment/flavors#conditionally-bundling-assets-based-on-flavor
 [Flutter fundamentals docs]: /get-started/fundamentals
 [Flutter install]: /get-started/install
 [Flutter web app initialization]: /platform-integration/web/initialization

src/content/assets/images/docs/flavors/flavors-android-icons.png

@@ -86,12 +86,6 @@ To do this, specify the asset files and transformer package in your pubspec file
 To learn how to do this and write your own asset-transforming packages, see
 [Transforming assets at build time][].
 
-### Conditional bundling of assets based on app flavor
-
-If your project utilizes the [flavors feature][], you can configure individual
-assets to be bundled only in certain flavors of your app.
-For more information, check out [Conditionally bundling assets based on flavor].
-
 ## Loading assets
 
 Your app can access its assets through an
@@ -536,5 +530,4 @@ For more details, see
 [MaterialApp]: {{site.api}}/flutter/material/MaterialApp-class.html
 [CupertinoApp]: {{site.api}}/flutter/cupertino/CupertinoApp-class.html
 [Transforming assets at build time]: /ui/assets/asset-transformation
-[Conditionally bundling assets based on flavor]: /deployment/flavors#conditionally-bundling-assets-based-on-flavor
 [flavors feature]: /deployment/flavors