feat: add workspace support to forc docs

[JoE11-y]

Description

Closes #4103

1. Noticed uncontrolled error when running the comand in contract/script/predicate, so cleaned up error handling.
2. Added tokio runtime to main function, due to http errors when compiling, for scenarios where library code is either imported from git or forc registry.
3. add support to workspaces.

Preview

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).
  • If my change requires substantial documentation changes, I have requested support from the DevRel team
• [] 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.
• I have requested a review from the relevant team or maintainers.

[IGI-111]

seems weird you'd need to include a full async runtime just to deal with some http errors, surely there are some synchronous facilities to do that even if the given library is written with an async client in mind.

Can you specifically explain the reasoning here?

[JoE11-y]

Oh yeah the actual error is this:

There is no reactor running must be called from the context of a tokio-1-x-runtime

Usually occurs if any of the library deps is from github or the forc registry.