.Net: Remove experimental attribute from the new function calling model classes

[SergeyMenshykh]

Removes the Experimental attribute from the new function-calling model classes and function call content classes as part of their graduation.

Corresponding tasks:

• .Net: Graduate function-calling content classes #6706
• .Net: Graduate new function calling model #8490

[stephentoub]

These are still only supported by the OpenAI connector, right? They're ignored by the Google one, the Mistral one, etc.?

[SergeyMenshykh]

These are still only supported by the OpenAI connector, right? They're ignored by the Google one, the Mistral one, etc.?

Yes, right, only the {Azure}OpenAI connectors use them.

[stephentoub]

These are still only supported by the OpenAI connector, right? They're ignored by the Google one, the Mistral one, etc.?

Yes, right, only the {Azure}OpenAI connectors use them.

And that will be fixed soon? Feels strange to say these are fully supported but then only have one of the built-in connectors support them.

[SergeyMenshykh]

These are still only supported by the OpenAI connector, right? They're ignored by the Google one, the Mistral one, etc.?

Yes, right, only the {Azure}OpenAI connectors use them.

And that will be fixed soon? Feels strange to say these are fully supported but then only have one of the built-in connectors support them.

We are graduating function-calling model classes and function-call content classes. The former are used by the {Azure}OpenAI connectors, and @RogerBarret0 was successfully able to use them to add function calling to the Ollama connect before the decision was made to go with OllamaSharp and the IChatClient implementation. The latter classes are used by {Azure}OpenAI and MistralAI connectors + Ollama try. Therefore, we believe they are in good shape for graduation.

Regarding adding function-calling support to the other connectors, as far as I understand, support will be added eventually when the connectors are prioritized, most likely after the Ignite event.
CC: @RogerBarret0, @markwallace-microsoft