ci: fix forc-fmt usage in CI when checking examples (FuelLabs#4153)

## Description

In the current form of `forc-fmt`, we should take the path to the
directory rather than the path to the Forc.toml.


## Checklist

- [ ] I have linked to any relevant issues.
- [ ] I have commented my code, particularly in hard-to-understand
areas.
- [ ] I have updated the documentation where relevant (API docs, the
reference, and the Sway book).
- [ ] 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.
- [ ] 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: spiral-ladder

.github/workflows/ci.yml

@@ -69,7 +69,7 @@ jobs:
           toolchain: ${{ env.RUST_VERSION }}
       - uses: Swatinem/rust-cache@v2
       - name: Check Sway examples formatting
-        run: cargo run --locked -p forc-fmt -- --check --path ./examples/Forc.toml
+        run: cargo run --locked -p forc-fmt -- --check --path ./examples
 
   build-mdbook:
     runs-on: ubuntu-latest