This issue tracks the work to add support for testing and inlining documentation code samples within the flutter/packages repository.

To ensure our documentation does not regress when moving material and cupertino to standalone packages (#101479), we must replicate the infrastructure from the flutter/flutter repository that tests our code samples, and inserts them in API documentation. This system ensures that code snippets displayed in the API docs are compilable, correct, and always in sync with the source code that is being tested.

This is a critical feature for preventing documentation from becoming outdated or containing errors, maintaining the high quality our developers expect, especially for the relocated material and cupertino packages.