Wire AndroidTypeResolverProvider and add ServiceLoader integration tests

[MessiasLima]

Description

Populate AndroidTypeResolverProvider.createResolvers() with every resolver added to :android in subsequent tickets, and add integration tests verifying ServiceLoader discovery and chain precedence. This ticket establishes the provider and test harness; each resolver ticket wires in its own resolver and extends the integration tests.

• Scope and constraints

  • Register all resolvers from subsequent tickets in AndroidTypeResolverProvider.createResolvers() returning the full list.
  • Resolvers requiring a strategy receive strategyProvider as first constructor arg; others receive only random.
  • Use Kotlin import aliases to resolve name collisions between Android SDK and Compose resolver packages (e.g., import dev.appoutlet.some.android.resolver.compose.ColorResolver as ComposeColorResolver).
  • Add an integration test class that wires a complete someSetup {} with some-android on the test classpath.
  • Follows the same ServiceLoader discovery pattern documented in docs/custom-resolvers.md.

• References

  • Spike: Spike: Plan some-android extension library #72
  • Prerequisites: Set up :android module with Android Library plugin and dependencies #75 (:android module setup)

Scope

In scope: populating the provider list, integration tests for end-to-end ServiceLoader discovery.
Out of scope: modifying resolver implementations, additional resolvers.

Acceptance criteria

• AndroidTypeResolverProvider compiles and is annotated with @AutoService(TypeResolverProvider::class)
• Integration test class exists with a someSetup {} + ResolverChain wired against some-android on the test classpath
• Integration test verifies some<String>() resolves through the chain (proves the provider is discovered and does not break the chain when returning an empty or partial resolver list)
• Provider structure is ready for resolver tickets to register their resolvers and add their own integration test cases
• Tests compile against android.jar with androidx.compose.ui:ui on classpath and run as JVM unit tests

[google-labs-jules]

Jules is on it. When finished, you will see another comment and be able to review a PR.

[google-labs-jules]

I apologize, but I encountered an unexpected error and wasn't able to complete the task.

[google-labs-jules]

Ready for a review! A PR has been created.

[google-labs-jules]

I apologize, but I encountered an unexpected error and wasn't able to complete the task.