Is your feature request related to a problem? Please describe.
While the variables: false option disables graphql.execute.variables logging, graphql.resolver.args is still unconditionally logged when resolvers: true is set. This means sensitive data passed as resolver arguments (e.g., mutation inputs) is recorded in spans even when users explicitly opt out of variable logging.
Describe the solution you'd like
When variables is false, graphql.resolver.args should also be omitted from resolver spans (relevant code).
Describe alternatives you've considered
Add a resolverArgs option (similar to the existing variables option) to control whether graphql.resolver.args is recorded in resolver spans.
Additional context