Update configureDependencyScanning mutation

What does this MR do?

As part of &4496 (closed), we've had to update the configureSecretDetection mutation to support an input variable instead of fullPath (those changes are part of !58230 (merged)). Since both configureSecretDetection and configureDependencyScanning are triggered by the same component and need to have the same schema, this MR updates configureDependencyScanning to align with Secret Detection.

Note: The configureDependencyScanning mutation isn't actually used at the moment. We have implemented the frontend ahead of the backend and this whole feature is currently behind a disabled-by-default feature flag. Thus, there is no risk in changing this as we'll be able to properly verify those changes as part of the backend MR.

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• 📋 Does this MR need a changelog?
  • I have included a changelog entry.
  • I have not included a changelog entry because _____.
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

Related to #282533 (closed)