F/ OS-441 test protocol upgrade

[Rekard0]

Description

Please include a summary of the change and be sure you follow the contributions rules we do provide here

Task: OS-441

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• I have selected the correct base branch.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• Any dependent changes have been merged and published in downstream modules.
• I ran all tests with success and extended them if necessary.
• I have updated the CHANGELOG.md file in the root folder.
• I have tested my code on the test network.

[heueristik]

The changes in this PR allow us to create deployment fixtures for specific OSx releases. I would approve this PR but we should merge #384 first.

A general comment:
It remains unclear how we will actually test the protocol upgrades in the future, given that Mathias tests them with tenderly, and that they become irrelevant once the upgrade happened.
I can imagine that these tests are important in the timeframe where we deployed the upgrade on a subset of the supported networks (e.g. the testnets while waiting with the the mainnet deployment). If meanwhile we continue working on the protocol, we want to be sure that the upgrade doesn't break because of this and tests could help in this regard.