`Valid_until` has to be taken into account``

### What

Since needs objects can now have the `valid_until` attribute this can make some needs no longer valid for the current version.
E.g. if the release is 1.2 but the need is only `valid_until: 1.0` then this need no longer is valid for this release and therefore should not be `checked` according to the metamodel etc. and not raise build errors.

### Acceptance Criteria (DoD)

Ensure that a need that has a `valid_until` attribute is no longer checked and raises NO build errors, if the attribute has a version higher than the release.

### How

Unsure yet how to implement this.