Use compiled binary output from forcto build Rust bindings

[digorithm]

Currently, we have a method under Contract to compile Sway code:

pub fn compile_sway_contract(
    project_path: &str,
    salt: Salt,
) -> Result<CompiledContract, Error> {
    let build_command = BuildCommand {
        debug_outfile: None,
        minify_json_abi: false,
        path: Some(project_path.into()),
        print_finalized_asm: false,
        print_intermediate_asm: false,
        binary_outfile: None,
        offline_mode: false,
        output_directory: None,
        silent_mode: true,
        print_ir: false,
        use_ir: false,
    };

    let (raw, _) =
        forc_build::build(build_command).map_err(|message| Error::CompilationError(message))?;

    Ok(CompiledContract { salt, raw })
}

Although that works fine, it adds a dependency on forc as a library. fuels-rs should be language agnostic: it should operate only on the compiled binary and the ABI, both targeting the FuelVM.

Recently, forc was updated to output the binary data to an output directory. fuels-rs can leverage that in order to remove the dependency on forc as a library. Instead of calling forc::build, take a path to the compiled binary data, the same way that it takes the path to the json ABI file.

Then, it would be on the user to use forc to generate the compiled binary and the json ABI file, then pass both to fuels-rs's deploy method and contract instantiation method (i.e. Contract::new()).