Fix origin remote and config file lookup errors

- Fix error when remote is not "origin" and fallback to alternate remotes if
  "origin" is not found
  - Add failure scenario to core integration test
- Fix error where "gfold.toml" not existing would result in execution
  failure
- Add config file lookup behavior to README
- Remove debug flag in favor of RUST_LOG
  - This also results in the logging module being removed since setting
    the logging should be configured via RUST_LOG
- Add RUST_LOG and RUST_BACKTRACE to README and CLI help troubleshooting
  sections
- Update display flags in README to use `-d`
- Update flag description for color to use "never" instead of "off" as
  one of its options
- Add sequencing debug logs (e.g. "foo has completed")
- Switch back to anyhow for its backtrace feature
- Update to 4.0.0-rc.2

Signed-off-by: Nick Gerace <nickagerace@gmail.com>

2 files changed, 3 insertions, 3 deletions

diff --git a/docs/DEVELOPING.md b/docs/DEVELOPING.md
index d990684..23b6607 100644
--- a/docs/DEVELOPING.md
+++ b/docs/DEVELOPING.md
@@ -18,9 +18,9 @@ Now, ensure that lints, tests, and builds succeed.
 ```shell
 cargo fmt --all -- --check
 cargo clippy -- -D warnings
-cargo doc
+cargo doc --all
 cargo test
-cargo build
+cargo build --all-targets
 ```
 
 > Alternatively, you can replace `cargo test` above with [cargo nextest](https://github.com/nextest-rs/nextest).
diff --git a/docs/RELEASE.md b/docs/RELEASE.md
index 3c0f43e..7d177c5 100644
--- a/docs/RELEASE.md
+++ b/docs/RELEASE.md
@@ -23,7 +23,7 @@ cargo build
 - [ ] Create and _do not merge_ a commit with the following message: `Update to <tag>`
 - [ ] Test and verify the publishing workflow:
 
-```bash
+```shell
 cargo publish --dry-run
 ```