Pipeline Failure on PR #993 Due to Potential Hardcoded Class Hash

[neotheprogramist]

After developing a new where API in PR #993, we have encountered a failure in the pipeline during the cargo test phase (details here: CI Run).

It appears that the issue may stem from modifications made to classes, possibly due to a hardcoded class hash. This is preventing the merging of PR dojoengine#993 as the pipeline fails to pass.

The task at hand is to verify whether the problem is indeed due to a hardcoded class hash. If confirmed, the necessary corrections should be implemented. If the hardcoded hash is not the cause, further investigation is required to identify the root of the problem and apply a fix.

[matzayonc]

Update:
Minimal problem: $ cargo nextest run --all-features tests::entities_test::tests::entities_test fails.
Observations:

• passes on local
• fails on CI
• fails on fresh clone

Conclusions:

• Files causing a problem are generated and outside of VCS

Possible fixes:

• Find a crate or contract that isn't build and add it to worflow or workspace

[matzayonc]

clone -> build -> checkout -> test works, but clone -> checkout -> build -> test does not.

[matzayonc]

Updated hardcoded address, and investigated possible alternatives.

• Capturing output of a program is unstable like shown here
• Modification of migraction contract passed to function - produces unclean code
• Modification of the return value as it isn't used almost anywhere