feat(contracts): adding the new availableExpectations field (#304)

[guzmud]

Proposed changes

• Adding new field availableExpectations to ContractExpectations

Testing Instructions

1. Need to be tested through an updated injector rather than as a stand-alone

Related issues

• Closes feat(contracts): add a availableExpectations field #304

Checklist

• I consider the submitted work as finished
• I tested the code for its functionality
• I wrote test cases for the relevant uses case
• I added/update the relevant documentation (either on github or on notion)
• Where necessary I refactored code to improve the overall quality
• For bug fix -> I implemented a test that covers the bug

Further comments

[Copilot]

Pull request overview

This PR updates the Python contract configuration models to align with the injector contract change described in #304 by adding support for an availableExpectations list alongside predefinedExpectations on the expectations contract field.

Changes:

• Add availableExpectations: List[Expectation] to ContractExpectations in the contracts config model.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.