add deprecated note to assertValidExecutionArguments

to notify theoretical users via deep import of imminent removal

Author: yaacovCR

Diff for: src/execution/execute.ts

@@ -246,6 +246,7 @@ function buildResponse(
  * Essential assertions before executing to provide developer feedback for
  * improper use of the GraphQL library.
  *
+ * @deprecated will be removed in v17 in favor of assertValidSchema() and TS checks
  * @internal
  */
 export function assertValidExecutionArguments(

Diff for: src/execution/subscribe.ts

@@ -19,6 +19,7 @@ import type {
   ExecutionResult,
 } from './execute';
 import {
+  // eslint-disable-next-line import/no-deprecated
   assertValidExecutionArguments,
   buildExecutionContext,
   buildResolveInfo,
@@ -160,6 +161,7 @@ export async function createSourceEventStream(
 
   // If arguments are missing or incorrectly typed, this is an internal
   // developer mistake which should throw an early error.
+  // eslint-disable-next-line import/no-deprecated
   assertValidExecutionArguments(schema, document, variableValues);
 
   // If a valid execution context cannot be created due to incorrect arguments,