Description

This PR adds support for logging in predicates via the use of theECAL opcode.
In theECAL implementation we simply replicate the functionality of theLOGD instruction - but for predicates.

Notes:

• To make this work we needed to create and propagate theenable_predicate_logs attribute in theBuildProfile,BuildConfig, andContext structs; this needed to be propagated down deep into their_generation so that the__log compiler intrinsic could branch based on theenable_predicate_logs attribute and the predicate programKind.
• With this change; theforc test --logs andforc test --raw-logs commands will now output logs for predicates.
• forc build will compile the predicate (which contains logs) indebug mode successfully
• forc build willNOT compile the predicate (which contains logs) inrelease mode
• scripts, contracts, libraries should remain unaffected by this change

Example

Predicate

predicate;pubstructCallParams {pubcoins:u64,pubgas:u64,}fnmain()->bool {letcall_params=CallParams {coins:7,gas:8,    };log(call_params);false}#[test]fntest_meaning_of_life() {log("test_meaning_of_life");assert(main()==false);}

> forc test --logs

> forc test --raw-logs

Checklist

• I have linked to any relevant issues.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation where relevant (API docs, the reference, and the Sway book).
  • If my change requires substantial documentation changes, I haverequested support from the DevRel team
• I have added tests that prove my fix is effective or that my feature works.
• I have added (or requested a maintainer to add) the necessaryBreaking* orNew Feature labels where relevant.
• I have done my best to ensure that my PR adheres tothe Fuel Labs Code Review Standards.
• I have requested a review from the relevant team or maintainers.