Fixes #2911, Add APIs to register custom uri functions for certain model

[xuzhg]

Fixes #2911, Add APIs to regiter custom uri functions for certain model

Avoid the global static setting
Avoid the overloads for different models
Use the Annotation to hold the custom Uri functions
Support the back-compatible

Copilot reviewed 4 out of 5 changed files in this pull request and generated no suggestions.

Files not reviewed (1)

• src/Microsoft.OData.Core/PublicAPI/net8.0/PublicAPI.Unshipped.txt: Language not supported

Comments skipped due to low confidence (3)

test/FunctionalTests/Microsoft.OData.Core.Tests/ScenarioTests/UriParser/CustomUriFunctionsTests.cs:701

• Ensure that the new behavior introduced by the changes is adequately covered by tests, including scenarios where the model is null and where it is not, as well as case-sensitive and case-insensitive function name matching.

private FunctionSignatureWithReturnType[] GetCustomFunctionSignaturesOrNull(IEdmModel model, string customFunctionName)

src/Microsoft.OData.Core/UriParser/CustomUriFunctions.cs:110

• The method SkipWhile should be replaced with Where to correctly filter out the specific function signature to remove.

FunctionSignatureWithReturnType[] customFunctionOverloadsWithoutTheOneToRemove = existingCustomFunctionOverloads.SkipWhile(funcOverload => AreFunctionsSignatureEqual(funcOverload, functionSignature)).ToArray();

src/Microsoft.OData.Core/UriParser/CustomUriFunctions.cs:75

• [nitpick] The error message string SRResources.CustomUriFunctions_AddCustomUriFunction_BuiltInExistsFullSignature should be checked for clarity and helpfulness.

throw new ODataException(Error.Format(SRResources.CustomUriFunctions_AddCustomUriFunction_BuiltInExistsFullSignature, functionName));