Use wildcard CompanionStatic rename to surface all class companions

The previous commit enumerated 7 specific Kotlin companion classes by name
across foundation-android (1), ui-graphics-android (1), and ui-text-android
(5). That fixed those 7 but left 62 more classes with the same problem in
just these three packages: ScrollState.Companion, LazyListState.Companion,
BlendMode.Companion, Brush.Companion, Path.Companion, ImeAction.Companion,
TextRange.Companion, AnnotatedString.Companion, and many others were still
unreachable without raw JNI.

Replace the per-class entries with the same wildcard XPath that
kotlin-stdlib, okio-jvm, com.google.ai.edge.aicore, and com.google.mlkit
genai-prompt already use:

    <attr path="/api/package/class[substring(@name,string-length(@name)-9)
          ='.Companion']"
          name="managedName">CompanionStatic</attr>

This renames every nested *.Companion peer in the package to CompanionStatic,
letting the binding generator emit `public static <Outer>.CompanionStatic
Companion { get; }` on every outer class.

After this change:

    foundation-android : 24 new static Companion accessors
    ui-graphics-android: 35 new static Companion accessors
    ui-text-android    : 45 new static Companion accessors
                        ---
                         104 total (vs. 7 in the previous revision)

Interface companions are unaffected — the binding generator hoists them to
top-level <Outer>Companion before this rename matches, so `Path.Companion`,
`ImageBitmap.Companion`, `DrawScope.Companion`, etc. surface correctly via
their hoisted peer.

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

Author: jonathanpeppers

source/androidx.compose.foundation/foundation-android/PublicAPI/PublicAPI.Unshipped.txt

@@ -77,12 +77,14 @@
     `<Outer>.Companion`, which collides with the static `Companion` property the
     generator would otherwise emit on the outer class (a nested type and a
     property can't share a name), so the field is silently dropped and the
-    singleton is only reachable via raw JNI. Rename the nested companion peer to
-    `CompanionStatic` (matching the okio binding convention) so the generator can
-    surface `public static KeyboardOptions.CompanionStatic Companion { get; }`,
-    letting consumers write `KeyboardOptions.Companion.Default` directly.
-    (Interface companions are unaffected — their peer is already hoisted/renamed,
-    so they surface without help.)
+    singleton is only reachable via raw JNI. Rename every nested `*.Companion`
+    peer to `CompanionStatic` (the same wildcard pattern kotlin-stdlib, okio,
+    aicore, and genai-prompt already use) so the generator surfaces
+    `public static <Outer>.CompanionStatic Companion { get; }` on every outer
+    class, letting consumers write e.g. `KeyboardOptions.Companion.Default`,
+    `ScrollState.Companion.Saver`, `LazyListState.Companion.Saver` directly.
+    (Interface companions are hoisted to top-level `<Outer>Companion` by the
+    generator before this rename matches, so they're unaffected.)
   -->
-  <attr path="/api/package[@name='androidx.compose.foundation.text']/class[@name='KeyboardOptions.Companion']" name="managedName">CompanionStatic</attr>
+  <attr path="/api/package/class[substring(@name,string-length(@name)-9)='.Companion']" name="managedName">CompanionStatic</attr>
 </metadata>