Added --bech32 flag to forc contract-id command

[ADTmux]

Description

Issue : https://github.com/FuelLabs/sway/issues/5842

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.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Amit Dave seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[ADTmux]

working on updating docs. Please feel free to let me know if any areas need rework/update

[kayagokalp]

Looking good! A possible issue with the dependency you added, so blocking for now as I need to make sure some stuff first. If that is the case I will provide you more guidance how to move around the issue with the dependency

[kayagokalp]

Suggested change

	// flag to display contract-id in bech32 format
	// Flag to display contract-id in bech32 format

[kayagokalp]

This dependency here will likely create an issue for us. Due to our internal procedures we require forc not to depend on sdk. We should be able to move around this somehow. I will think about a different way of doing this but first I wanted to make sure this is not allowed by our CI.

[kayagokalp]

Also please run cargo fmt so that CI fails go away :) and make sure to run cargo build and commit the cargo.lock file since you added a depenedncy cargo.lock should be changed. But that is not commited here.

[ADTmux]

@kayagokalp I did see the fact that we are generating the documentation for all forc commands in the Sway Book by running forc --help, but could I get any pointers to any past PRs (of how the html files are built), or as to how we are doing that? I want to add the --bech32 in the Sway Book.

[kayagokalp]

@kayagokalp I did see the fact that we are generating the documentation for all forc commands in the Sway Book by running forc --help, but could I get any pointers to any past PRs (of how the html files are built), or as to how we are doing that? I want to add the --bech32 in the Sway Book.

Hey, no worries about that we have a mdbook preprocessor that automatically does that. So it is done via CI not manually