In port it is possible to have cyclic relations - e.g. issue belong to service, service has relation for most recent issue - these can't be properly defined in the pulumi provider as there is no way to properly set the depends on and in a clean org / pulumi up it can't add either blueprint first because the related blueprint doesn't exist

This issue was identified with aggregation properties and countered by separating them out into their own resource despite in port being defined on the blueprint so it would be helpful to have a similar resource for relations to allow this cyclical relations to be made