remove archived forc-explore plugin from CI and docs (#7257)

## Description
This repo was [archived ](https://github.com/FuelLabs/forc-explorer )in
July 2024 but was not removed from CI or the docs.
I have update the plugins section of the documentation from forc explore
to `forc-install` which is a
[tool](https://github.com/DarthBenro008/forc-install) from a community
member.

## Checklist

- [x] I have linked to any relevant issues.
- [ ] I have commented my code, particularly in hard-to-understand
areas.
- [x] I have updated the documentation where relevant (API docs, the
reference, and the Sway book).
- [x] If my change requires substantial documentation changes, I have
[requested support from the DevRel
team](https://github.com/FuelLabs/devrel-requests/issues/new/choose)
- [ ] I have added tests that prove my fix is effective or that my
feature works.
- [ ] I have added (or requested a maintainer to add) the necessary
`Breaking*` or `New Feature` labels where relevant.
- [x] I have done my best to ensure that my PR adheres to [the Fuel Labs
Code Review
Standards](https://github.com/FuelLabs/rfcs/blob/master/text/code-standards/external-contributors.md).
- [x] I have requested a review from the relevant team or maintainers.

Author: JoshuaBatty

.github/workflows/ci.yml

@@ -245,7 +245,6 @@ jobs:
           for dir in ./forc-plugins/*/; do
                 cargo install --locked --path "$dir"
           done
-          cargo install --locked forc-explore
       - name: Install mdbook-forc-documenter
         run: cargo install --locked --path ./scripts/mdbook-forc-documenter
 

.github/workflows/gh-pages.yml

@@ -34,7 +34,6 @@ jobs:
           cargo install --locked --debug --path ./forc-plugins/forc-migrate
           cargo install --locked --debug --path ./forc-plugins/forc-node
           cargo install --locked --debug --path ./forc-plugins/forc-publish
-          cargo install --locked --debug forc-explore
       - name: Install mdbook-forc-documenter
         uses: actions-rs/cargo@v1
         with:

ci_checks.sh

@@ -29,7 +29,6 @@ cargo install --locked --debug --path ./forc-plugins/forc-fmt &&
 cargo install --locked --debug --path ./forc-plugins/forc-lsp &&
 cargo install --locked --debug --path ./forc-plugins/forc-client &&
 cargo install --locked --debug --path ./forc-plugins/forc-tx &&
-cargo install --locked --debug forc-explore &&
 cargo install --locked --debug --path ./scripts/mdbook-forc-documenter &&
 forc build --path sway-lib-std &&
 forc test --path sway-lib-std &&

docs/book/README.md

@@ -23,7 +23,6 @@ You must also install forc plugins that are already documented within the book.
 ```sh
 cargo install --path ./forc-plugins/forc-client
 cargo install --path ./forc-plugins/forc-doc
-cargo install forc-explore
 cargo install --path ./forc-plugins/forc-fmt
 cargo install --path ./forc-plugins/forc-lsp
 ```

docs/book/src/SUMMARY.md

@@ -107,7 +107,6 @@
     - [forc crypto](./forc/plugins/forc_crypto.md)
     - [forc debug](./forc/plugins/forc_debug.md)
     - [forc doc](./forc/plugins/forc_doc.md)
-    - [forc explore](./forc/plugins/forc_explore.md)
     - [forc fmt](./forc/plugins/forc_fmt.md)
     - [forc lsp](./forc/plugins/forc_lsp.md)
     - [forc migrate](./forc/plugins/forc_migrate.md)

docs/book/src/forc/plugins/forc_explore.md

@@ -1,32 +1,29 @@
 # Plugins
 
-Plugins can be used to extend `forc` with new commands that go beyond the native commands mentioned in the previous chapter. While the Fuel ecosystem provides a few commonly useful plugins (`forc-fmt`, `forc-client`, `forc-lsp`, `forc-explore`), anyone can write their own!
+Plugins can be used to extend `forc` with new commands that go beyond the native commands mentioned in the previous chapter. While the Fuel ecosystem provides a few commonly useful plugins (`forc-fmt`, `forc-client`, `forc-lsp`, `forc-migrate`), anyone can write their own!
 
-Let's install a plugin, `forc-explore`, and see what's underneath the plugin:
+Let's install a plugin, `forc-install`, and see what's underneath the plugin:
 
 ```sh
-cargo install forc-explore
+git clone https://github.com/darthbenro008/forc-install
+cd forc-install
+cargo install --path .
 ```
 
-Check that we have installed `forc-explore`:
+Check that we have installed `forc-install`:
 
 ```console
 $ forc plugins
 Installed Plugins:
-forc-explore
+forc-install
 ```
 
-`forc-explore` runs the Fuel Network Explorer, which you can run and check out for yourself:
+`forc-install` is a tool to manage GitHub dependencies in your Forc.toml file: For example, to install a sway library hosted on github:
 
 ```console
-$ forc explore
-Fuel Network Explorer 0.1.1
-Running server on http://127.0.0.1:3030
-Server::run{addr=127.0.0.1:3030}: listening on http://127.0.0.1:3030
+forc install https://github.com/user/sway-library
 ```
 
-You can visit <http://127.0.0.1:3030> to check out the network explorer!
-
 Note that some plugin crates can also provide more than one command. For example, installing the `forc-client` plugin provides the `forc deploy` and `forc run` commands. This is achieved by specifying multiple `[[bin]]` targets within the `forc-client` manifest.
 
 ## Writing your own plugin

docs/book/src/forc/plugins/index.md

@@ -21,7 +21,7 @@ MDBOOK_preprocessor__FORC_documenter__STRICT="true" mdbook build docs/book
 Enter a new entry under the `Commands` section within `SUMMARY.md`, in this format:
 
 ```md
-- [forc explore](./forc_explore.md)
+- [forc fmt](./forc_fmt.md)
 ```
 
 ### Adding a new forc plugin

scripts/mdbook-forc-documenter/README.md

@@ -104,8 +104,8 @@ mod tests {
     #[test]
     fn test_get_forc_command_from_file_name() {
         assert_eq!(
-            "forc explore",
-            get_forc_command_from_file_name(OsString::from("forc_explore.md")),
+            "forc fmt",
+            get_forc_command_from_file_name(OsString::from("forc_fmt.md")),
         );
     }
 }