Kr/union type handling

[rocktavious]

Resolves #

Problem

The RelationshipResource is a union type so its ambigous which type is the return value.

Solution

The best i can find this is the correct way to do this but it mucks with the GraphQL generation turning

{id,source{__typename,... on Domain{id,aliases},... on InfrastructureResource{id,aliases,name},... on Service{id,aliases},... on System{id,aliases},... on Team{alias,id}},target{__typename,... on Domain{id,aliases},... on InfrastructureResource{id,aliases,name},... on Service{id,aliases},... on System{id,aliases},... on Team{alias,id}},type}

into

{id,source,target,type}

and i'm not entirely sure why.

Checklist

• I have run this code, and it appears to resolve the stated issue.
• This PR does not reduce total test coverage
• This PR has no user interface changes or has already received approval from product management to change the interface.
• Does this change require a Terraform schema change?
  • If so what is the ticket or PR #
• Make a changie entry that explains the customer facing outcome of this change