Add caveat to @graphql-eslint/require-id-when-available

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Label this issue
• Close this issue

The following discussion from !96422 (merged) should be addressed:

• @leetickett started a discussion:

  We should not be deploying frontend changes which rely on backend changes in the same release!

I added the id field to CiJobArtifactType and the linter "forced me" to update the frontend, when in fact, I should have waited till the next release: https://docs.gitlab.com/ee/development/multi_version_compatibility.html

I suspect we now ensure all new types have an id property, so I guess this is very unlikely to happen again, but perhaps worth a little investigation?