chore: fix markdown reported by clippy in docs

[Br1ght0ne]

Summary

While running cargo clippy, I get a few warnings about Markdown formatting in our doc comments (see the dropdown for warning text). This should both clean my cargo output and guarantee proper formatting on docs.rs.

excerpt of `cargo clippy` output

warning: doc list item missing indentation
  --> packages/fuels-code-gen/src/program_bindings/abigen.rs:34:9
   |
34 |     /// for, and of what nature (Contract, Script or Predicate).
   |         ^
   |
   = help: if this is supposed to be its own paragraph, add a blank line
   = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_lazy_continuation
   = note: `#[warn(clippy::doc_lazy_continuation)]` on by default
help: indent this line
   |
34 |     ///   for, and of what nature (Contract, Script or Predicate).
   |         ++

warning: doc list item missing indentation
   --> packages/fuels-code-gen/src/program_bindings/abigen.rs:154:9
    |
154 |     /// generated.
    |         ^
    |
    = help: if this is supposed to be its own paragraph, add a blank line
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_lazy_continuation
help: indent this line
    |
154 |     ///   generated.
    |         ++

warning: `fuels-code-gen` (lib) generated 2 warnings
warning: doc list item missing indentation
   --> packages/fuels-programs/src/calls/call_handler.rs:297:9
    |
297 |     /// Note that this is a builder method, i.e. use it as a chain:
    |         ^
    |
    = help: if this is supposed to be its own paragraph, add a blank line
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_lazy_continuation
    = note: `#[warn(clippy::doc_lazy_continuation)]` on by default
help: indent this line
    |
297 |     ///   Note that this is a builder method, i.e. use it as a chain:
    |         ++

warning: `fuels-programs` (lib) generated 1 warning

Checklist

• All changes are covered by tests (or not applicable)
• All changes are documented (or not applicable)
• I reviewed the entire PR myself (preferably, on GH UI)
• I described all Breaking Changes (or there's none)

[calldelegation]

Hello @Br1ght0ne can we change the title to chore: fix markdown reported by clippy in docs so the release notes script can pick it up on the next release please? 😄

[Br1ght0ne]

@calldelegation Sure! Should I/we avoid scoping (parenthesised parts) altogether in the future?

[calldelegation]

@Br1ght0ne yea the titles should be chore, feat, or fix | chore!, feat!, or fix!
https://github.com/FuelLabs/fuels-rs/blob/master/scripts/change-log/src/get_full_changelog.rs#L159-#L175

[digorithm]

@Br1ght0ne, can you please sync the branch?