Rename forc doc --manifest-path to --path

[amiremohamadi]

Description

Closes #5789

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.

[fuel-cla-bot]

Thanks for the contribution! Before we can merge this, we need @amiremohamadi to sign the Fuel Labs Contributor License Agreement.

[zees-dev]

There are still references to the manifest-path in the github workflow files; these will also need to be updated as part of the PR.

[ironcev]

Thanks for the contribution 😄 ❤️

[ironcev]

@bitzoic We use to mark the breaking changes in the forc CLI with the breaking_change label and also to explain the change in the PR for devs who will eventually need to migrate their, e.g. CI scripts.

I would expect the same here. If devs, e.g., generate docs as a CI step this could break their workflows.

UPDATE: @amiremohamadi found a good solution for avoiding breaking change altogether, by adding the old manifest-path as an alias for the new path.

[bitzoic]

Thank you!