inter-repository automated testing

[eagmon]

When vivarium-core updates, it has the potential to break many other vivarium projects. Because of this, it would be useful to implement automated testing that can check other repos before making changes to vivarium-core. Here is a link to some useful discussion about how this could be done: https://blog.marcnuri.com/triggering-github-actions-across-different-repositories/

[U8NWXD]

One alternative approach would be to treat Vivarium Core as a library that those other repositories depend on, just like Numpy is a library we depend on. Numpy doesn't incorporate our tests into their testing workflow; instead, they precisely define their API and then write tests to make sure that API works. If we were to adopt a similar strategy, we would focus on making sure our API is clear and rigorously tested. That way, we could avoid breaking any other code that uses Vivarium, even if that code's tests aren't available to us