chore!: remove built-in binaries for forc and fuel-core

[petertonysmith94]

Closes #2084
Closes #2277

---

Summary

• Internalises the forc and fuel-core binaries (removed usage for end-consumer).
• Adds the ability to pass in custom binary paths via forcPath and fuelCorePath to the fuels.config.ts.
  • Defaults to forc and fuel-core
• Binary not found and version mismatches errors for fuels CLI.
• Suppressed the following related logs (experienced in the CI):

/bin/sh: 1: fuel-core: not found
/bin/sh: 1: forc: not found

Breaking change

1. Built-in binaries have been removed, so the following means of running forc or fuel-core are not available.

# Before
npx fuels forc
npx fuels-forc
# AND
npx fuels core
npx fuels-core

Suggested to install fuelup and associated binaries (forc and fuel-core).

# After
forc
fuel-core

2. fuels.config - removed options useBuiltinForc and useBuiltinFuelCore

3. launchNode - removed option for useSystemFuelCore

---

Scenarios

Both instances will stop the process until the issue/s are resolved.

1. Non-existent binaries

> [email protected] fuels:dev /fuel/0.0.0-pr-2143-20240513112950
> fuels dev

Unable to find the following binaries on the filesystem:
 -> 'forc' at path 'forc'
 -> 'fuel-core' at path 'fuel-core'

Visit https://docs.fuel.network/guides/installation/ for an installation guide.

2. Version mismatch

> [email protected] fuels:dev /fuel/0.0.0-pr-2143-20240513112950
> fuels dev

The following binaries on the filesystem are outdated:
 -> 'forc' is currently '0.55.0', but requires '0.56.1'.
 -> 'fuel-core' is currently '0.23.0', but requires '0.26.0'.

[petertonysmith94]

Converted to draft to implement the changes as proposed here and here.

Furthering the scope of this review, so dismissing review :)

[nedsalk]

Suppressed the following related logs (experienced in the CI):

/bin/sh: 1: fuel-core: not found
/bin/sh: 1: forc: not found

Why would you suppress these logs? Do you know the underlying cause of them?

[petertonysmith94]

Suppressed the following related logs (experienced in the CI):

/bin/sh: 1: fuel-core: not found
/bin/sh: 1: forc: not found

Why would you suppress these logs? Do you know the underlying cause of them?

Turns out they were not just outputted to our CI, and were being displayed to the end-user when running npx fuels versions or similar.

It was introduced here, and appears to be when the command errors we'd pipe this to stderr - we now ignore this.

[arboleya]

Good stuff! 🚀

Changes made :)

[github-actions]

Coverage Report:

Lines	Branches	Functions	Statements
79.73%(-0.05%)	70.64%(-0.09%)	76.82%(+0%)	79.81%(-0.05%)

Changed Files:

Ok	File (✨=New File)	Lines	Branches	Functions	Statements
🔴	packages/account/src/test-utils/launchNode.ts	100% (+0%)	85.18% (-3.28%)	68.42% (+0%)	94.23% (-0.05%)
🔴	✨ packages/create-fuels/scripts/rewriteTemplateFiles.ts	0% (+0%)	100% (+100%)	100% (+100%)	0% (+0%)
✅	✨ packages/fuels/src/cli/commands/withBinaryPaths.ts	100% (+100%)	100% (+100%)	100% (+100%)	100% (+100%)
🔴	✨ packages/utils/src/cli-utils/tryFindBinaries.ts	100% (+100%)	76.47% (+76.47%)	100% (+100%)	100% (+100%)