Remove rules_ios example and maintenance commitments

MAINTENANCE.md

@@ -13,8 +13,7 @@ healthy by:
 - Ensuring changes don’t break existing projects as much as possible (e.g.
   maintaining Bazel, rules, and Xcode version backwards compatibility)
 - Participating in idea and design discussions
-- Adding support for new Bazel, rules (e.g. rules_apple, rules_swift,
-  rules_ios), and Xcode versions
+- Adding support for new Bazel, rules (e.g. rules_apple, rules_swift), and Xcode versions
 - Keeping CI green
 
 ## Access control

README.md

@@ -41,7 +41,6 @@ on it, or [file a new issue][file-an-issue]!
   - Core Bazel C/C++/Objective-C
   - rules_swift
   - rules_apple
-  - rules_ios
   - Most likely your custom rules as well!
 - Minimal configuration needed (see the [usage](#usage) section below)
 - It “just works”

examples/README.md

@@ -8,9 +8,6 @@ This directory holds several examples using rules_xcodeproj. To open an example,
 * **integration**
     <br> Contains many targets to exercise all of the [rules_apple](https://github.com/bazelbuild/rules_apple/tree/master/doc) rules, along with various ways of using rules_xcodeproj itself (e.g. multi-platform consolidated targets, Xcode Previews, device support, etc.).
 
-* **rules_ios**
-    <br> Contains targets to exercise [rules_ios](https://github.com/bazel-ios/rules_ios) macros and rules.
-
 * **sanitizers**
     <br> Contains targets to test Sanitizers in BwB mode. The main purpose is to make sure sanitizers in BwB mode work and give UI feedback the same way sanitizers do in BwX builds.