chore(aggregation-mode): prevent rebuilding programs if not changed

[MarcosNicolau]

Description

Since we introduced deterministic buildings with docker for the zkvm programs the proof aggregator started to take too much time to compile. This got even worse after the multilayer feature. This pr, recompiles the programs only if they have changed. For that, we've been orthodox and simply solved it by hashing the files + features.

This means that now the programs have to be compiled only once for each feature (prove, gpu)

To test it I suggest removing the use_docker options for faster builds in build.rs

Type of change

• Optimization

Checklist

• “Hotfix” to testnet, everything else to staging
• Linked to Github Issue
• This change depends on code or research by an external entity
  • Acknowledgements were updated to give credit
• Unit tests added
• This change requires new documentation.
  • Documentation has been added/updated.
• This change is an Optimization
  • Benchmarks added/run
• Has a known issue
  • Link to the open issue addressing it
• If your PR changes the Operator compatibility (Ex: Upgrade prover versions)
  • This PR adds compatibility for operator for both versions and do not change batcher/docs/examples
  • This PR updates batcher and docs/examples to the newer version. This requires the operator are already updated to be compatible

[JuArce]

These prints are not displayed

[MarcosNicolau]

Build scripts communicate with Cargo by printing to stdout. Cargo will interpret each line that starts with cargo:: as an instruction that will influence compilation of the package. All other lines are ignored.

These flags indicate that the build.rs should run if the file outputted has been modified. They weren't really working for me that is why the hash solution was applied. Right now, they are there just in case. You can read more in the source.

Source: https://doc.rust-lang.org/cargo/reference/build-scripts.html#outputs-of-the-build-script

[MauroToscano]

This should be done with a makefile, I'm making another pr to solve this issue:

#1962