Track and test dependencies' 'next' branch

[tgonzalezorlandoarm]

parsec depends on several repositories under the parallaxsecond organization.

Currently, when testing the main branch of parsec, fixed versions of the latest released crates of those repositories are being used. A problem may arise when there is a change introduced in the main/'next' branch of those repositories that would break parsec when updating/incorporating that change. This is currently not being tested in our CI. As parsec release is dependent on having published the dependencies' crates, there are issues that will not be caught until the publishing of said crates.

• Add nightly jobs that use ci.sh --next-branch-tracking to test the next release branches of parallaxsecond repositories and spot issues before release. These jobs make use of previously defined re-usable actions and utils/release_tracking.py

[tgonzalezorlandoarm]

Please check the added test results in my fork:

• https://github.com/tgonzalezorlandoarm/parsec/actions/runs/6774233114

[tgonzalezorlandoarm]

I will generate, after this one gets merged, a follow up PR creating a utils/cargo-commands.py for gathering together the cargo calls from the 2 scripts that we have in the utils/ directory right now. I will also be simplifying the re-usable actions there.

[tgonzalezorlandoarm]

https://github.com/tgonzalezorlandoarm/parsec/actions/runs/6786709261 new test on my fork after these changes

[tgonzalezorlandoarm]

https://github.com/tgonzalezorlandoarm/parsec/actions/runs/6786705099

[tgonzalezorlandoarm]

https://github.com/tgonzalezorlandoarm/parsec/actions/runs/6800846830 New CI run

[tgonzalezorlandoarm]

https://github.com/tgonzalezorlandoarm/parsec/actions/runs/6853736203