Create integration test for create fuels

[arboleya]

Summary

The idea is that every PR would publish a PR tag and have an install/assertion routine.

The automation would probably need to drive the UI and assert the results.

Below are the steps of how one could do it manually:

Manual Steps

1. Ensure you have the correct versions of forc and fuel-core:

 fuelup component add forc@0.55.0
 fuelup component add fuel-core@0.24.3

2. Scaffold a new project using the next tag:

pnpm create fuels@next

3. Make the scaffolded app to use the next tag:

cd ./my-app-name # <—— add app name here
pnpm add fuels@next

4. Run fuels dev in terminal 1

pnpm fuels:dev

5. Run next dev in terminal 2

pnpm dev

Final Notes

This flow will test all CLIs (below) at once and also the SDK's basic functionality:

1. create-fuels
2. fuels
3. fuels-typegen

Sub-issues

• Add e2e tests for the create fuels template app #2264
• Add a 'live' automated testing suite for create fuels #2265

[arboleya]

This would also satisfy all requirements of this older issue:

• CI tests: Add a process to build, pack and install the libs on each PR #568