Add TryValidate for ODataQueryOptions

[WanjohiSammy]

Issues

This pull request fixes #1419.

Description

This PR introduces a TryValidate methods to ODataQueryOptions addressing the current limitation where query options can only be validated by throwing exceptions.

The TryValidate method provides a way to validate query options without relying on exception handling. Instead of relying on exception handling, this method returns a bool indicating success or failure and provides detailed validation errors through an out parameter.

Example Usage:

var filterOption = new FilterQueryOption("Name eq 'John'", context);
var settings = new ODataValidationSettings();

if (_validator.TryValidate(filterOption, settings, out IEnumerable<string> validationErrors))
{
    Console.WriteLine("Validation succeeded!");
}
else
{
    Console.WriteLine("Validation failed:");
    foreach (var error in validationErrors)
    {
        Console.WriteLine(error);
    }
}

Checklist (Uncheck if it is not completed)

• Test cases added
• Build and test with one-click build and test script passed

Additional work necessary

If documentation update is needed, please add "Docs Needed" label to the issue and provide details about the required document change in the issue.

[WanjohiSammy]

/AzurePipelines run OData-AspNetCoreOData-main-rolling-1ES

[azure-pipelines]

No pipelines are associated with this pull request.

[WanjohiSammy]

/AzurePipelines run OData-AspNetCoreOData-main-rolling-1ES

[azure-pipelines]

No pipelines are associated with this pull request.

[WanjohiSammy]

/AzurePipelines run OData-AspNetCoreOData-main-rolling-1ES

[azure-pipelines]

No pipelines are associated with this pull request.

[xuzhg]

In this pattern, shall we call 'Validate' within 'TryValidate' and avoid duplicate the validation codes?

[xuzhg]

To avoid breaking changes, can we use the default interface method so we don't avoid the breaking changes?

[xuzhg]

Is it the time to add 'async' interface method?