Remove built-in binaries

[arboleya]

Summary

• Remove all built-in binaries (however, keep them for the internal SDK purposes only).
• Favouring the fuelup toolchain (w/ forc and fuel-core) for the end-user prerequisites.

[arboleya]

Turns out this page is not even shown in the current menu.

• https://docs.fuel.network/docs/nightly/fuels-ts/fuels/

Although it exists and can be reached via links in other pages:

• https://docs.fuel.network/docs/nightly/fuels-ts/fuels/binaries/

[petertonysmith94]

@arboleya as well as removing the documentation references to these tools, I was thinking of the following:

• Removing useBuiltinFuelCore and useBuiltinForc from fuels config.
  I believe forcBuildFlags still has an application.
• Removing forc and core commands from Fuels CLI and making these internal scripts.

What do you think?

[arboleya]

Agreed. 💯

We should also mark packages/{forc,fuel-core} packages as private: true.

They would still be available to the workspace via the fuels- prefix:

• pnpm fuels-forc
• pnpm fuels-core

The above should suffice for building contracts and running tests in CI, but the packages won't be published to NPM.

One key benefit of this change is that we will no longer have to deal with NPM post-install scripts, which can be considered a net positive for increased Bun support. cc @Dhaiwat10

[petertonysmith94]

I was thinking of moving them into the internal/{forc,fuel-core} directory, and setting private: true.

Any thoughts on this?

[arboleya]

Makes sense. 👍