Handle compatibility with dev version of AgentsExampleZoo better

[Tortar]

Since #875 has some problems I do this separately, see #875 (comment) for why we need this

edit: actually #875 is fine because also #946 has the same errors, but both work locally. However, let's merge this separately anyway since it is more sensible anyway

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (cbb8140) 85.71% compared to head (560ec35) 85.71%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #956   +/-   ##
=======================================
  Coverage   85.71%   85.71%           
=======================================
  Files          36       36           
  Lines        2542     2542           
=======================================
  Hits         2179     2179           
  Misses        363      363           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Tortar]

Strangely enough this works instead, github is crazy :S

Maybe it is that this is more recent pr (?), so merging the other two before this one will be enough to make CI happy, this is my bet :D

[Datseris]

The existence of this PR highlights why one should avoid circular dependencies in packages.

[Tortar]

I think that it actually higlights this when both packages depends on unreleased versions. We are in this strange situation because of this. When both packages will be released, there will be no problem like this anymore, it will be as if the models where inside Agents.jl. We will just pin the major version on both packages to ensure everything works.

I think the only problem which could arise is that if we make a major version of Agents without updating AgentsExampleZoo he will need a downgrade of Agents. But this will never happen if we don't completely forget about AgentsExampleZoo :D

[Datseris]

I think that it actually higlights this when both packages depends on unreleased versions.

The same problem will also always happen for every major version change in either package.

[Datseris]

In any case, let's just get this in for now and we can consider more how to deal with it before releasing v6.