feat: update delivery function handler interface

[BasKiers]

In the PH on Tuesday we discussed the following changes

• Revert the handler map to a handler function using type unions
• Add a helper to make "type save" event handlers
• Add a isIntrospectionQuery boolean to the graphql.query event.
• Allow GraphQLQueryArgument to be a Record<string, string> to allow for multi-argument GraphQLQueryField calls. The record key would be the argument name, the key value a JSON Pointer (not set in stone, we might use a different string format) that points to the JSON property that needs to be extracted from the field value and provided as the argument value.

[andipaetzold]

Can you update the PR title? "PH discussion" is not suitable for a public npm package changelog ;)

[kdamball]

Will also need a change the template code, right?

[kdamball]

Should this also be part of Field mapping too?

[BasKiers]

I'm not sure if I'm following. This boolean is used to indicate wether the query being sent for this event is an introspection query. An app can use this to easily overwrite where the schema is loaded from, for instance by loading it from the file system instead of passing the introspection query along to the 3rd party GraphQL API.

[anho]

Can we adjust the graphQLQueryArgument of GraphQLFieldTypeMapping as well?

[anho]

GraphQLFieldTypeMappingResponse should be the following:

export type GraphQLFieldTypeMappingResponse = {
  namespace: string
  fields: GraphQLFieldTypeMapping[]
}

[contentful-automation]

🎉 This PR is included in version 2.4.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀