Functional requirement not in environment packages but still works

[SamyCoenen]

Expected Result

If a functional requirement is not in the environment packages it should not create automation jobs and the policy fails.

Actual Result

If a service only contains a single functional requirement, it doesn't seem to check the packages

Steps To Reproduce

Potential Causes, Fixes or Additional Information

[GBrawl]

The issue here is that when updating a stack instance the policies do not get validated again. When creating a stack instance this works correctly.