`@deprecated` for relation fields

[kasir-barati]

So I read this issue: #104

But my case is something like this:

model User {
  /// @deprecated use userProfile instead
  profile @relation(fields: [profileId], references: [id])
  
  // BUT we cannot defined same relation twice in Prisma!!!
  userProfile @relation(fields: [profileId], references: [id])

  profileId String!
}

Any comment on this?

[kasir-barati]

Also if we do not have any other solution except rolling this breaking change out suddenly, that then goes against one of the core concepts of GraphQL which is giving our client time to adapt to new API and remove something when nobody is using it.