unify directives presentation

[rsill-neo4j]

added a number of "tba" in comments. mostly missing definitions, but on some occasions i wasn't sure which parts of the follow-up sections could got to the "usage" subsection.

[lidiazuin]

Looking good, just a few suggestions and questions.

[mjfwebb]

Suggested change

	=== Definition
	// tba

It's too complicated to put as a definition.

[mjfwebb]

There's a specific version for validate:

[source, graphql, indent=0]
----
"""
This is a simpler version of the authentication directive to be used in the validate-document step.
"""
directive @authentication(
  """operations"""
  operations: [String]
  jwt: String
) on OBJECT | FIELD_DEFINITION | SCHEMA
----

[mjfwebb]

Suggested change

	=== Definition
	// tba

As with authorization this is too complicated to write a simple definition for, I think.

There exists a "simple" case for validate:

[source, graphql, indent=0]
----
"""
This is a simpler version of the authorization directive to be used in the validate-document step.
"""
directive @authorization(
  """filter"""
  filter: [String]
  """validate"""
  validate: [String]
) on OBJECT | FIELD_DEFINITION
----

[mjfwebb]

Suggested change

	=== Definition
	// tba

Same as others.

[source, graphql, indent=0]
----
"""
This is a simpler version of the subscriptionsAuthorization directive to be used in the validate-document step.
"""
directive @subscriptionsAuthorization(
  """filter"""
  filter: [String]!
) on OBJECT | FIELD_DEFINITION
----

[neo-technology-commit-status-publisher]

Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.

[neo-technology-commit-status-publisher]

💔 All backports failed

Status	Branch	Result
❌	6.x	Backport failed because of merge conflicts You might need to backport the following PRs to 6.x: - wording changes, added a link
❌	7.x	Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

backport --pr 211

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details