feat: Extend automated ingredient validation to include argSelector ingredients (#2641)

[mansiverma897993]

Description

This PR extends the automated ingredient validation framework to include argSelector ingredients, resolving a bug where providing empty or invalid values to argSelector inputs (like cipher modes or key/IV source options) caused unhandled runtime exceptions instead of clean validation errors.

How it addresses the issue:

1. src/core/Ingredient.mjs:
2. • Detects if the ingredient is of type argSelector.
3. • Resolves array-like defaultValue configurations to their selected index string (checkVal[this.defaultIndex ?? 0]?.name || "") to prepare for validation checks.
4. • Updates the empty check logic (isAllowedOptionEmpty) to check if any of the option names is "".
5. • Adds validation to map each object in the defaultValue array to its name property, filters out optgroups ([Group 1]), and verifies that checkVal matches one of the permitted options case-insensitively.
6. src/node/api.mjs:
7. • Updates the transformArgs wrapper mapping so that omitted argSelector arguments automatically resolve to their default string option (e.g. "CBC" or "Off") instead of remaining an array of configuration objects, which would trigger runtime exceptions inside the operations.
8. tests/operations/tests/AutomatedValidation.mjs:
9. • Configured AutomatedValidationTestOp to include a test argSelector ingredient.
10. • Added unit test coverage for valid, invalid, and empty values of argSelector type.
      Closes Feature request: Extend automated ingredient validation to include "argSelector" ingredients #2641

[mansiverma897993]

@GCHQDeveloper581 take a look and leeme know if any changes required !!