Use dynamic supported fuel-core version

[Br1ght0ne]

Close #1189. Waiting on a new fuel-core release incorporating FuelLabs/fuel-core#1473.

Checklist

• I have linked to any relevant issues.
• I have updated the documentation.
• I have added tests that prove my fix is effective or that my feature works.
• I have added necessary labels.
• 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.

[digorithm]

I know this hasn't been your focus lately, but is there any updates on this?

[iqdecay]

Looks good! Just a question.

[segfault-magnet]

Some notes:

• Using a build.rs is problematic because this will cause our users to always depend on fuel-core since we're packaging a build.rs dependent on fuel-core that will run when users build their software. One of the motivations for the fuel-core-lib is to lower compile times for live demos.
• We need a CI check that when the fuel-core version in the workspace cargo toml is updated the corresponding version file matches the version in the toml.
• If we're to generate version files we might as well generate a rust file that has a pub const version: ... = VERSION_HERE. Better yet if there is a const version structure so that we don't have to do any parsing in runtime.

Maybe it is enough to have that version.rs file with a unpublished binary that checks if the versions match. Something like the docs checker binary currently run in the CI.

Also keep in mind that sometimes our fuel-core versions are git checkouts, when there are circularly dependent breaking changes between the compiler, core and us. The CI should allow for this (unless we're publishing).

[hal3e]

LGTM