Improve remote config patches documentation

[LukasPaczos]

Task/Issue URL: https://app.asana.com/1/137249556945/project/1208671518894266/task/1213611390820529?focus=true

Description

• Rewrites the README for conciseness and readability; adds a Quick Start section
• Adds build variant warning (patches only work in internal builds)
• Documents patch ordering, conflict resolution, and failure behaviour
• Adds "Writing a patch file" section with examples for overriding feature state, sub-features, and adding new sub-features
• Clarifies when the full patch (hash removal + version bump) is needed vs. a simple state override
• Adds "Verifying a patch was applied" section covering Gradle build output and logcat
• Restructures usage: local dev via local.properties vs. committed patches via -Pconfig_patches flag
• Adds Maestro test file layout example and end-to-end build+test workflow
• Adds GitHub Actions workflow example using checkout-and-assemble gradle_flags input
• Adds PR review workflow: how to share patch files in a PR description so reviewers can verify feature flag states step by step
• Adds patch examples section with full before/after config for common scenarios

Steps to test this PR

• Read through the updated README and verify accuracy
• Verify the Maestro and GitHub Actions examples match existing workflow patterns in the repo

🤖 Generated with Claude Code

[GerardPaligot]

The new versioning value and concrete examples with sub features are really nice improvements!

[LukasPaczos]

Thanks for taking a look @GerardPaligot! I gave this another pass, incorporated your ideas, and re-did the structure to keep it more concise at the top and add more examples at the bottom.

This is ready for another round.

[GerardPaligot]

LGTM!