Align CLI flags with Xcode (#266)

* Align CLI flags with Xcode

When doing a build from the CLI it should align with what Xcode is doing

This is also required to make sure `xchammer_dev_repo` points to the
right place

Additionally, I've made a few improvements and added better guidance on
debugging

.bazelrc

@@ -1,8 +1,14 @@
 # A few settings for XCHammer's .bazelrc
+# Notes:
 # Debugging: Use the remapping feature of rules_swift.
+# cpu: This needs to be set to align with what Xcode is using
+# compilation_mode: This is overriden for release in Xcode
 build \
+ --compilation_mode dbg \
  --announce_rc \
  --spawn_strategy=standalone \
  --strategy=SwiftCompile=worker \
  --swiftcopt=-Xwrapped-swift=-debug-prefix-pwd-is-dot \
- --experimental_strict_action_env=true
+ --experimental_strict_action_env=true \
+ --cpu darwin_x86_64 \
+ --experimental_show_artifacts

Docs/XCHammerFAQ.md

@@ -103,9 +103,10 @@ build --override_repository=xchammer=/path/to/xchammer/
 
 For binary integration / out of tree builds, `make xchammer_dev_repo` allows a
 `WORKSPACE` to consume XCHammer built out of tree but point to the latest build,
-symlinked in `bazel-bin`. Add to the repository in question:
+symlinked in `bazel-out`. Add to the repository in question:
 ```
-build --override_repository=xchammer=/path/to/xchammer/bazel-bin/xchammer_dev_repo
+build \
+    --override_repository=xchammer=/path/to/xchammer/bazel-out/darwin_x86_64-dbg/bin/xchammer_dev_repo
 ```
 
 This makes it easy and pain free to build XCHammer outside of the repo but pull
@@ -118,7 +119,7 @@ artifact or local source repository in question, for using the dev repo as
 mentioned above:
 ```
 build \
-    --override_repository=xchammer=/path/to/xchammer/bazel-bin/xchammer_dev_repo/
+    --override_repository=xchammer=/path/to/xchammer/bazel-out/darwin_x86_64-dbg/bin/xchammer_dev_repo
 ```
 
 2. In XCHammer repo, run `make workspace_v2 && open workspace_v2.xcodeproj`
@@ -130,6 +131,13 @@ build \
 5. Trigger project gen in the iOS repository via bazel ( e.g. `bazlisk build
 :MyProject`, `make xcode_focus`, or whatever way you build the Xcode project) 
 
+Note: The rule `xcode_project` is cache invalidated so the binary doesn't run
+everytime you build with Bazel. This means if you want to constantaly re-run the
+binary you'll need to remove the outputs each time. For example, for the Bazel
+target `//:FocusXcodeProj` and project `Focus.xcodeproj`
+```
+rm -rf bazel-bin/Focus.xcodeproj && bazel build :FocusXcodeProj
+```
 
 ### How should I contribute to XCHammer?